Skip to content

docs: use chronus version --only for single-package hotfix bumps - #5045

Draft
weidongxu-microsoft wants to merge 1 commit into
mainfrom
docs/hotfix-chronus-only
Draft

docs: use chronus version --only for single-package hotfix bumps#5045
weidongxu-microsoft wants to merge 1 commit into
mainfrom
docs/hotfix-chronus-only

Conversation

@weidongxu-microsoft

Copy link
Copy Markdown
Member

Documents passing + '--only ' + to + 'pnpm chronus version' + during a hotfix release.

Why

On a + '
elease/*' + branch there are often unrelated pending change files (tcgc, benchmark, playground, website). Running + 'pnpm chronus version --ignore-policies' + without + '--only' + consumes ALL of them and bumps unrelated packages. Passing + '--only ' + bumps just the target package(s) and consumes only their change files — so you don't need to know or manually remove the other pending change files.

Changes

    • 'CONTRIBUTING.md' + — hotfix release step now uses + '--only ' + .
    • '.github/skills/hotfix-release/SKILL.md' + — version bump step updated with + '--only' + and a warning.

Doc-only change ( + '.md' + files are excluded from chronus change detection, so no changeset needed).

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com
Copilot-Session: cd6f2e08-d6d3-42ae-affd-bc71e98086f7

Document passing --only <package-name> to pnpm chronus version during a hotfix
release so only the hotfixed package(s) are bumped and only their change files
are consumed. Without --only, unrelated pending change files on the release
branch are consumed and unrelated packages get bumped.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: cd6f2e08-d6d3-42ae-affd-bc71e98086f7
@github-actions

Copy link
Copy Markdown
Contributor

No changes needing a change description found.

@azure-sdk-automation

Copy link
Copy Markdown
Contributor

You can try these changes here

🛝 Playground 🌐 Website

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants