[issues/646_start_new_release] Auto-create branch on release:start#649
Conversation
## Summary After publishing a release, `release:start` prepares the repo for the next development cycle by adding an `[Unreleased]` section to CHANGELOG and restoring the `[!IMPORTANT]` banner to README. Previously it did this in-place on whatever branch you were on. Now it detects when you are on `main` and creates a `post-release-v<VERSION>` branch first. ## Changes - `start-release.sh`: added step 0 that checks the current branch. If on `main`, creates `post-release-v<VERSION>` and switches to it. Otherwise applies changes in-place. - `CHANGELOG.md`: `[Unreleased]` section prepended (mechanical script output) - `README.md`: `[!IMPORTANT]` banner restored (mechanical script output) ## Test Plan - [x] All existing tests pass - [ ] Manual: run `pnpm release:start:vscode-extension` from `main` and verify a branch is created ## Related - Closes #646
|
Warning Review limit reached
More reviews will be available in 19 minutes and 55 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
✅ CI / Integration Tests (with overrides) — run summaryDuration: 0m 56s QA TC IDs: 2 exercised across 0 features Report: View run & artifacts Reproduce locally: Feature breakdown
|
✅ CI / Integration Tests (automated) — run summaryDuration: 11m 6s QA TC IDs: 161 exercised across 0 features Report: View run & artifacts Reproduce locally: Feature breakdown
|
✅ CI / Integration Tests (with extensions) — run summaryDuration: 13m 4s Unit tests: Ran in separate Test & Validate job QA TC IDs: 193 exercised across 0 features Report: View run & artifacts Reproduce locally: Feature breakdown
|
Summary
After publishing a release,
release:startprepares the repo for the next development cycle by adding an[Unreleased]section to CHANGELOG and restoring the[!IMPORTANT]banner to README. Previously it did this in-place on whatever branch you were on. Now it detects when you are onmainand creates apost-release-v<VERSION>branch first.Changes
start-release.sh: added step 0 that checks the current branch. If onmain, createspost-release-v<VERSION>and switches to it. Otherwise applies changes in-place.CHANGELOG.md:[Unreleased]section prepended (mechanical script output)README.md:[!IMPORTANT]banner restored (mechanical script output)Test Plan
pnpm release:start:vscode-extensionfrommainand verify a branch is createdRelated