v0 requests pullfrog@^0.1.58, but npm latest is 0.1.57 — every @v0 workflow fails with ETARGET (half-published release?) #78

Hi pullfrog team!
Ive been using pullfrog just fine the past few days. However, this morning it started failing unexpectedly.

Observations

Since about ~2026-08-17 18:51 UTC, uses: pullfrog/pullfrog@v0 fails in ~9 s at the "Run agent" step in my github pull request flow.

» running pullfrog@^0.1.58 via /home/runner/actions-runner/cached/2.336.0/externals/node24/bin/npx
npm error code ETARGET
npm error notarget No matching version found for pullfrog@^0.1.58.

Reproducible without CI: npx pullfrog@^0.1.58 --version → same ETARGET.

Why — it looks like a half-fired release. The git tag v0.1.58 exists in this repo and v0 points at it (0acee8dc), but:

• there is no v0.1.58 GitHub release (releases stop at v0.1.57, 2026-08-15T01:27Z), and
• npm view pullfrog dist-tags.latest → 0.1.57 (registry last modified 2026-08-15T01:27Z) — 0.1.58 was never published to npm.

So the action tag moved ahead of the package it installs. The same unchanged workflow on our repo ran green several times earlier on 2026-08-17, which brackets the breakage to the v0 tag move.

Possible correlation: #76 (chore(deps): replace semver with verkit, merged 2026-08-16T23:02Z) touches version/release tooling — this may be the first release through the new path, with the tag push succeeding and the npm publish silently not.

Impact: every workflow tracking @v0 currently fails on all triggers.

Ask: publish 0.1.58 to npm, or point v0 back at the 0.1.57 commit.

Thanks for pullfrog — it caught real bugs for us this week; happy to provide the failing run logs if useful.