refactor(release): split workflow into npm-publish and release-notes jobs#578
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 Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release workflow is restructured to split publishing and release notes into two conditional jobs. Triggers now support both tag pushes and manual dispatch. The npm-publish job resolves a dist_tag from the release tag pattern and publishes via OIDC authentication. The release-notes job creates GitHub releases idempotently, syncs changelog content, and commits changes back to a tag-derived target branch. ChangesRelease Workflow and Package Publishing Restructure
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
commit: |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release.yml:
- Around line 126-132: Validate the tag exists and mark prereleases explicitly:
before running gh release create "$TAG" use gh release view "$TAG" to ensure the
tag exists and fail otherwise (do not let gh create a missing tag), call gh
release create with --verify-tag to prevent creating tags implicitly, and add
--prerelease when the TAG contains a dash (e.g., check if "$TAG" contains '-'
and include the --prerelease flag) so prerelease semantics are set correctly;
update the conditional around gh release view/gh release create and adjust the
create command to include --verify-tag and the conditional --prerelease flag.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3babc1d8-9c08-4f4f-b089-43ed64e73590
📒 Files selected for processing (2)
.github/workflows/release.ymlscripts/release.sh
💤 Files with no reviewable changes (1)
- scripts/release.sh
Description
Linked Issues
Additional context
Summary by CodeRabbit