Skip to content

fix(release): use npm staged publishing - #29

Merged
2chevskii merged 1 commit into
masterfrom
fix/npm-staged-release
Oct 4, 2026
Merged

2chevskii merged 1 commit into
masterfrom
fix/npm-staged-release

Conversation

@2chevskii

Copy link
Copy Markdown
Owner

The npm trusted publisher permits staged publishing, so direct publication of v1.0.1 was rejected while GitHub Packages succeeded. Use npm stage publish with the latest tag; maintainers approve the staged package with 2FA before it becomes publicly available.

Allow manually publishing an existing release to one selected registry using the current workflow. This lets v1.0.1 reuse its existing release tarball without republishing to GitHub Packages or moving the Git tag. Document staging, approval, and recovery in AGENTS.md.

Validation: actionlint passed with its outdated ubuntu-26.04 label check excluded; changed-file formatting and git diff --check passed. The preceding release build and all checks succeeded. Hosted staging will be verified after merge.

@2chevskii
2chevskii merged commit 2b65ed9 into master Oct 4, 2026
5 checks passed
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