chore(CI): clean up pre-releases during release#3792
Conversation
|
Warning Rate limit exceeded
⌛ 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates two GitHub Actions release workflows by adding a cleanup job for pre-releases and pinning the semantic-release action to a specific version across both workflows. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
|
Deployed to https://pr-3792.aam-digital.net/ |
There was a problem hiding this comment.
Pull request overview
Adds an automated cleanup step to the manual release workflow to remove old *-master* pre-release GitHub releases/tags before running semantic-release, helping keep the repository’s release/tag namespace tidy during official releases.
Changes:
- Introduces a new
pre-releases-cleanupjob that deletes GitHub releases whose tag names contain-masterand cleans up matching remote git tags. - Keeps existing
semantic-releasejob for generating the stable release.
You can also share your feedback on Copilot code review. Take the survey.
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/create-release.yml:
- Around line 9-10: The release job is running in parallel with
pre-releases-cleanup; make release depend on pre-releases-cleanup so cleanup
always finishes first by adding a needs: [pre-releases-cleanup] entry to the
release job definition (and likewise add needs where the other duplicate release
job definition appears around the second occurrence referenced). Locate the
GitHub Actions job blocks named pre-releases-cleanup and release and add the
needs key to the release job to ensure serialization.
- Around line 22-24: The pipeline can fail when grep returns exit code 1 if
there are no "-master" tags; update the pipeline invoking gh release list | grep
'\-master' so the grep non-zero exit doesn't fail the step (e.g., append "||
true" to the grep command or otherwise coerce its exit to 0) before piping into
the while loop that reads tags (the sequence around gh release list --repo ...
--jq '.[].tagName' | grep '\-master' | while read -r tag; do).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: f29e00ca-e25c-49b7-a449-d9d169c2d114
📒 Files selected for processing (2)
.github/workflows/create-release.yml.github/workflows/on-master-push.yml
Summary by CodeRabbit