Add trusted publishing and CI example - #5
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ac25a3104b
ℹ️ 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: actions/checkout@v7 | ||
| - uses: actions/setup-node@v7 |
There was a problem hiding this comment.
Use released action major versions
The official release histories for actions/checkout and actions/setup-node currently stop at v6, so GitHub cannot resolve either @v7 reference and every push/PR CI run fails before installing dependencies. The same unavailable versions also block the new .github/workflows/publish.yml release job, while the setup-node reference breaks the copyable example workflow; pin these references to released majors.
Useful? React with 👍 / 👎.
What changed
Why
Future releases should be reproducible, provenance-backed, and independent of long-lived npm publish tokens. Users also need a practical CI example.
Validation
npm test(12 passing)npm run checknpm run pack:checkgitleaks dir . --redactgit diff --check