Skip to content

Add dry-run verification to publish workflow - #2

Merged
cowboyd merged 1 commit into
mainfrom
verify-package-builds
Mar 1, 2026
Merged

cowboyd merged 1 commit into
mainfrom
verify-package-builds

Conversation

@cowboyd

@cowboyd cowboyd commented Mar 1, 2026

Copy link
Copy Markdown
Collaborator

Motivation

The publish workflow builds and publishes to both npm and JSR in a single shot. If one registry publish succeeds but the other build is broken, we end up with a half-published release that's painful to recover from.

Approach

Add verify-jsr and verify-npm gate jobs that perform dry-run publishes before the real thing. Both publish-npm and publish-jsr now depend on both verify jobs passing. The npm build artifact is uploaded once during verification and reused in the publish step to avoid rebuilding.

Previously the publish workflow would build and publish to both npm and
JSR in a single shot. If the JSR publish succeeded but the npm build was
broken (or vice versa), we'd end up with a half-published release that's
painful to recover from.

Now verify-jsr and verify-npm run dry-run publishes first, and the real
publish jobs only proceed once both pass. The npm build artifact is
uploaded once and reused so the publish step doesn't rebuild.
@cowboyd
cowboyd merged commit a1d8da4 into main Mar 1, 2026
1 of 2 checks passed
@cowboyd
cowboyd deleted the verify-package-builds branch March 1, 2026 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant