Skip to content

feat(release): document linked-versions policy#482

Merged
tmchow merged 1 commit into
mainfrom
feat/release-please-config-fix
Apr 1, 2026
Merged

feat(release): document linked-versions policy#482
tmchow merged 1 commit into
mainfrom
feat/release-please-config-fix

Conversation

@tmchow

@tmchow tmchow commented Apr 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Documents the intentional linked-versions policy that keeps cli and compound-engineering at the same version
  • Explains the known upstream release-please limitation where exclude-paths filtering is overridden by linked-versions synced bumps
  • Prevents reviewers from flagging these version bumps as unnecessary

Triggered by review feedback on #474 where a reviewer flagged the CLI version bump as unjustified.

🤖 Generated with Claude Code

@tmchow tmchow changed the title docs: document linked-versions release policy docs(cli): document linked-versions release policy Apr 1, 2026
Explains the intentional cli/compound-engineering version linkage so
reviewers don't flag synced bumps as unnecessary.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@tmchow tmchow force-pushed the feat/release-please-config-fix branch from ed485a1 to 90d0790 Compare April 1, 2026 20:42
@tmchow tmchow changed the title docs(cli): document linked-versions release policy feat(release): document linked-versions policy Apr 1, 2026
@tmchow tmchow merged commit 96345ac into main Apr 1, 2026
2 checks passed
@github-actions github-actions Bot mentioned this pull request Apr 1, 2026
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.

1 participant