Skip to content

ci: propose minor releases for breaking changes - #481

Closed
chrispader wants to merge 1 commit into
mainfrom
ci/breaking-as-minor
Closed

chrispader wants to merge 1 commit into
mainfrom
ci/breaking-as-minor

Conversation

@chrispader

Copy link
Copy Markdown
Member

Release Please proposes a major release whenever a commit is marked as breaking, as it did with 11.0.0 in #479 after the ESM-only change in #475. We want breaking changes to ship as minor releases, and Release Please has no setting for that once a package is past 1.0.

This adds a breaking-as-minor versioning strategy and selects it in release-please-config.json. It works like the default strategy, except that a release containing breaking changes becomes a minor release. The changelog still lists them under the breaking changes heading. A Release-As: X.0.0 commit footer still releases a new major version.

fix: ...                     10.2.0 → 10.2.1
feat: ...                    10.2.0 → 10.3.0
chore!: ...                  10.2.0 → 10.3.0   (was 11.0.0)
Release-As: 11.0.0           10.2.0 → 11.0.0

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
react-native-nitro-sqlite Ready Ready Preview Nov 10, 2026 11:10am UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — 1b9a516d Deployed Nov 10, 2026 by vercel[bot]
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