Repository navigation
ci: trunk-based releases, semver policy and release notes with PR links - #30
Merged
Merged
Conversation
- Drop the staging branch: feature branches open PRs straight into master, and the Changesets "version packages" PR is the batching step. CI no longer runs on pushes to staging. - The auto-changeset step ignores docs- and test-only changes, so users only get a new version when shipped code or dependencies change. - Changelogs and GitHub Releases come from @changesets/changelog-github and link each entry to its PR. - CONTRIBUTING documents the semver policy (patch/minor/major) and the plan to cut 1.0.0 together with the Odoo refactor.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A release used to take three PRs (feature →
staging→master→ version packages), andstagingdrifted behindmasterafter every release. On top of that,0.0.xpatch-only versions told users nothing about breaking changes.What changes
staging→mastermaster. The version packages PR is the batching step.masterandstagingmaster, plus every PR*.md,test/,vitest.config.jsand.prettierignore, so docs-only changes never publish@changesets/changelog-github: each entry links its PR1.0.0planned with the Odoo refactorVerification
obsidian, because that PR also changedobsidian/package.jsonfiles;db,odoo.pnpm install --frozen-lockfileandpnpm audit --audit-level=highpass.@changesets/changelog-github@1.0.1is 40 days old.changelog-githubneedsGITHUB_TOKENduringchangeset version.changesets/actionalready gets it inrelease.yml, and the manual release command in CONTRIBUTING now passesgh auth token.After merge
Delete the
stagingbranch: it has no commits that are not already inmaster.