fix: use npm for publish #228
Conversation
|
Warning Rate limit exceeded@ChiragAgg5k has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 10 minutes and 22 seconds before requesting another review. ⌛ 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. 📒 Files selected for processing (1)
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. 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 |
266948b to
10d33ca
Compare
There was a problem hiding this comment.
Pull request overview
This PR switches from using bun publish to npm publish for publishing packages to npmjs, adding support for provenance attestation through OIDC authentication. The change aims to leverage npm's built-in provenance feature for enhanced supply chain security.
Key changes:
- Adds Node.js setup step to configure npm registry authentication
- Updates npm to the latest version for OIDC support
- Switches publish commands from
bun publishtonpm publish --provenance
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
10d33ca to
31351ec
Compare
31351ec to
12f86f7
Compare
No description provided.