chore: release via GitHub Actions with staged publishing - #81
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a
releaseworkflow like honojs/hono: on tag push, it runsnpm stage publish --provenancewith trusted publishing (OIDC). A maintainer then approves the staged package on npmjs.com.The release script is now
np --no-publish, same as honojs/hono. np handles the version bump, tag, push, and GitHub release. Publishing happens only in CI, so np no longer hits the OTP prompt. Release steps are in AGENTS.md.Before merging: add
honojs/cli+release.ymlas a trusted publisher for@hono/clion npmjs.com.The author should do the following, if applicable
pnpm run format:fix && pnpm run lint:fixto format the code