Skip to content

[issues/646_start_new_release] Auto-create branch on release:start#649

Merged
couimet merged 1 commit into
mainfrom
issues/646_start_new_release
Jun 13, 2026
Merged

[issues/646_start_new_release] Auto-create branch on release:start#649
couimet merged 1 commit into
mainfrom
issues/646_start_new_release

Conversation

@couimet

@couimet couimet commented Jun 13, 2026

Copy link
Copy Markdown
Owner

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

  • All existing tests pass
  • Manual: run pnpm release:start:vscode-extension from main and verify a branch is created

Related

## 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
@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@couimet, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 37e0e600-cb82-4357-b633-e92bb7838762

📥 Commits

Reviewing files that changed from the base of the PR and between 0b20c8f and fdc76f3.

📒 Files selected for processing (3)
  • packages/rangelink-vscode-extension/CHANGELOG.md
  • packages/rangelink-vscode-extension/README.md
  • packages/rangelink-vscode-extension/scripts/start-release.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch issues/646_start_new_release

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 and usage tips.

@couimet couimet merged commit 6e39fe9 into main Jun 13, 2026
7 checks passed
@couimet couimet deleted the issues/646_start_new_release branch June 13, 2026 01:25
@github-actions

Copy link
Copy Markdown

✅ CI / Integration Tests (with overrides) — run summary

Duration: 0m 56s

QA TC IDs: 2 exercised across 0 features

Report: View run & artifacts

Reproduce locally: ./scripts/run-integration-tests.sh --label needs-override --exclude-label cursor --exclude-assisted

Feature breakdown
Feature TCs IDs

@github-actions

Copy link
Copy Markdown

✅ CI / Integration Tests (automated) — run summary

Duration: 11m 6s

QA TC IDs: 161 exercised across 0 features

Report: View run & artifacts

Reproduce locally: ./scripts/run-integration-tests.sh --exclude-label requires-extensions --exclude-label cursor --automated

Feature breakdown
Feature TCs IDs

@github-actions

Copy link
Copy Markdown

✅ CI / Integration Tests (with extensions) — run summary

Duration: 13m 4s

Unit tests: Ran in separate Test & Validate job

QA TC IDs: 193 exercised across 0 features

Report: View run & artifacts

Reproduce locally: ./scripts/run-integration-tests.sh --exclude-label cursor --exclude-label needs-override --exclude-assisted

Feature breakdown
Feature TCs IDs

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.

QA Checklist — v2.0.0

1 participant