docs: update release steps with version file and patch release steps - #194
docs: update release steps with version file and patch release steps#194slashpai wants to merge 2 commits into
Conversation
Align the release guide with cut-PR practice so VERSION stays in sync with the GPG-signed tag pushed to rhobs/obs-mcp. Signed-off-by: Jayapriya Pai <janantha@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: slashpai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Warning Review limit reached
Next review available in: 12 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
Document release-X.Y branches, cherry-pick PRs into the release line, and tagging from that branch so patches do not pick up unrelated main commits. Signed-off-by: Jayapriya Pai <janantha@redhat.com>
e47af28 to
3f92878
Compare
|
@iNecas could you please take a look? |
| git push <fork> release-vX.Y.Z | ||
| git add CHANGELOG.md VERSION | ||
| git commit -m "chore: cut vX.Y.Z" | ||
| git push <fork> cut-vX.Y.Z |
There was a problem hiding this comment.
Nitpick: There is some inconsistency when referencing the remotes, <fork> vs <remote> vs <upstream-remote>. Perhaps <fork-remote> and <upstream-remote> would be probably better.
|
small nitpick, but good to go otherwise. |
cc: @iNecas