chore: switch to npm staged publishing#221
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: aaefb3947c
ℹ️ 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: JS-DevTools/npm-publish@0fd2f4369c5d6bcfcde6091a7c527d810b9b5c3f # v4 | ||
| with: | ||
| token: empty | ||
| run: pnpm stage publish --no-git-checks |
There was a problem hiding this comment.
When this release job runs from a fresh checkout, dist/ and client/ are ignored and have no tracked files, but package.json publishes only those generated directories and points exports/types at dist. With the build step removed, the pnpm stage publish step stages the package before those artifacts exist; I verified the resulting dry-run pack contains only LICENSE, README.md, and package.json, so approving the staged release would ship missing entrypoints to npm.
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: