ci: configure release-please for the 2.0.0 beta line - #54
Conversation
Flagsmith/github-webhook-handler runs release-please centrally for any repo that has release-please-config.json and .release-please-manifest.json at its root, so no workflow is checked in here — and a .github/workflows file whose name contains "release-please" would opt the repo back out. `versioning: prerelease` and `prerelease: true` are both required: the strategy strips the -beta suffix and hands back a bare major.minor.patch unless `prerelease` is set. Together they keep the beta line on 2.0.0-beta.N for every commit type until we flip `prerelease` off, at which point the next release is exactly 2.0.0. The manifest starts at the last npm release, 1.1.0, whose tag sits on the commit below `feat!: CLI v2` — so the first release considers exactly that commit, and Release-As pins it to a numbered beta instead of the bare 2.0.0-beta that bumpPrerelease would produce from a version with no prerelease digits. beep boop Release-As: 2.0.0-beta.1
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
2 participants
Contributes to #45.
The
release-pleasecheck onmaincurrently reports "release-please is not configured for this repository"; once we merge this, it should go green, with a release PR proposing 2.0.0-beta.1.Important
Release-As: 2.0.0-beta.1footer. Squash-and-merge keeps it by default for a single-commit branch — just don't edit it out of the body.prerelease: truealso marks the GitHub release as a prerelease, and that can't be decoupled from the versioning.GET /releases/latestskips prereleases, so Addinstall.sh#44'sinstall.shmust resolve the newest tag from/releasesuntil we're out of public beta.