Skip to content

ci: publish releases on tag push without a changelog - #15

Merged
phanan merged 1 commit into
mainfrom
ci/publish-releases-on-tag-push
Jul 1, 2026
Merged

phanan merged 1 commit into
mainfrom
ci/publish-releases-on-tag-push

Conversation

@phanan

@phanan phanan commented Jul 1, 2026

Copy link
Copy Markdown
Member

What

  • Drop --draft from the release job so a pushed v* tag publishes its release automatically.
  • Drop --generate-notes so the release body stays empty.
  • Remove the maintainer-only "How releases are cut" section from the README.

Why

The release job created every release as a --draft and nothing ever published them, so every franken release since the repo launched sat unpublished — invisible to anyone following the README's "download from the Releases page" instructions, with asset URLs that 404 for anonymous download. Publishing on tag push fixes that at the source.

The README's "How releases are cut" section documented internal release mechanics (draft assets, tag/version conventions, FrankenPHP pinning) that are irrelevant to users downloading a binary.

Drop --draft so tagged releases go live automatically instead of piling
up as unpublished drafts, and drop --generate-notes so the release body
stays empty. Also remove the maintainer-only 'How releases are cut'
section from the README.
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 42 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: f5c3de9b-57a1-41c6-b83a-10dc7f83b762

📥 Commits

Reviewing files that changed from the base of the PR and between b423f61 and 89bdb17.

📒 Files selected for processing (2)
  • .github/workflows/release.yml
  • README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/publish-releases-on-tag-push

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.

@phanan
phanan merged commit 437dc01 into main Jul 1, 2026
2 checks passed
@phanan
phanan deleted the ci/publish-releases-on-tag-push branch July 1, 2026 23:05
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