chore: switch to npm staged publishing#118
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed32d16523
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| uses: ncipollo/release-action@339a81892b84b4eeb0f6e744e4574d79d0d9b8dd # v1 | ||
| with: | ||
| generateReleaseNotes: 'true' | ||
| run: pnpm stage publish --no-git-checks |
There was a problem hiding this comment.
On v* tag pushes this job now ends after pnpm stage publish, and the previous ncipollo/release-action step plus contents: write permission were removed; I checked the release workflow/repo references and there is no other GitHub Release creation left. If staged publishing is meant to replace only the npm publish operation, tagged releases will no longer get GitHub release entries or generated notes, so keep the release step (and write permission) after the staging step.
Useful? React with 👍 / 👎.
1 participant
This PR switches the release workflow to npm staged publishing with
pnpm stage publishand aligns the repository package manager metadata onpnpm@11.3.0.Related Links: