Skip to content

ci(nightly): stop tagging the repo for every nightly build#652

Open
andyne13 wants to merge 1 commit into
developfrom
feature/nightly-image-only
Open

ci(nightly): stop tagging the repo for every nightly build#652
andyne13 wants to merge 1 commit into
developfrom
feature/nightly-image-only

Conversation

@andyne13

@andyne13 andyne13 commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

The /tags page is cluttered with nightly-* and dev-* git tags, drowning the real v* releases.

Cause: build_dev.yml created a GitHub Release (via ncipollo/release-action) per nightly — and a Release requires a git tag. The ray job did it again with a -ray suffix, so 2 git tags per night. The cleanup-old-dev-releases job only pruned nightly-* releases (not dev-*, and tag deletion was best-effort), so tags accumulated.

Fix: nightlies are now image-only artifacts. Removed both Create development release steps and the cleanup job. The nightly still builds and pushes to ghcr with nightly, dev-latest, and nightly-YYYYMMDD-sha Docker tags (traceability preserved); it no longer writes any git tag or Release. Also dropped contents: write (least privilege — no longer needed).

Result: /tags will only ever show real v* releases going forward. A separate one-time purge will remove the existing nightly-*/dev-* tags.

@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@andyne13, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9f7f368a-4347-420e-b78f-560631b54d6a

📥 Commits

Reviewing files that changed from the base of the PR and between 760531e and be0dbf3.

📒 Files selected for processing (1)
  • .github/workflows/build_dev.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/nightly-image-only

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@andyne13 andyne13 marked this pull request as ready for review July 8, 2026 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant