ci(release): publish npm alphas under alpha tag#51
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 37 minutes and 18 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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.
Code Review
This pull request updates the release readiness documentation (docs/RELEASE_READINESS.md) to include instructions for viewing npm distribution tags and explicitly using the --tag alpha flag when publishing alpha versions locally. It also clarifies that alpha versions are published under the alpha dist-tag rather than latest. There are no review comments to address, so no additional feedback is provided.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
Updates the npm publishing workflow and release-readiness documentation so prerelease (alpha) versions can be published successfully by using an explicit alpha dist-tag, aligning with npm’s requirement for prerelease publishing.
Changes:
- Update GitHub Actions npm publish step to include an
alphadist-tag. - Document dist-tag verification and local publish instructions for alpha releases.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/RELEASE_READINESS.md | Adds guidance to verify npm dist-tags and updates local publish instructions to use --tag alpha. |
| .github/workflows/npm-publish.yml | Adds --tag alpha to the npm publish command in the GitHub Actions workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - name: Publish package | ||
| if: steps.published.outputs.already != 'true' | ||
| run: npm publish --access public | ||
| run: npm publish --access public --tag alpha |
Summary
Why
npm error You must specify a tag using --tag when publishing a prerelease version.Validation