fix: use trusted publishing for packages#236
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9536b14688
ℹ️ 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".
9536b14 to
67d8ab7
Compare
Summary
NPM_TOKENandNODE_AUTH_TOKENfrom the Changesets publish step.changesets/action@v1takes its no-changesets path and publishes the already-versioned, unpublished@mrtdown/coreand@mrtdown/fspackages.Root Cause
The merged package publish run reached
changeset publish, but npm returnedE404 Not Found ... or you do not have permissionfor both@mrtdown/core@2.0.0-alpha.23and@mrtdown/fs@2.0.0-alpha.23. The workflow was passingsecrets.NPM_TOKEN, so npm attempted token-based publish with a token that does not have publish rights for the@mrtdownscope. The repository already hasid-token: write, so the workflow should use npm trusted publishing instead.Validation
npm run checknpm run changeset -- status --since origin/main