build: migrate release tooling from standard-version to Changesets#129
Merged
Conversation
Replaces the conventional-commits-driven standard-version flow with Changesets for changelog/version management: - CI-driven release via changesets/action: opens/updates a Version Packages PR on push to master and publishes on merge, using npm trusted publishing (OIDC) instead of a long-lived NPM_TOKEN, with GitHub Releases enabled. - Keep GitHub-linked changelog entries via @changesets/changelog-github. - Drop the PR-title conventional-commit lint and Renovate's :semanticCommits preset, since nothing consumes that format anymore. - Renovate dependency PRs get no automatic changeset, matching prior behavior where deps bumps didn't trigger a release on their own. - Backfill a changeset for the unreleased breaking change in #126 (object-based menu API), filed as minor rather than major to stay in the 0.x range per this project's convention. Two manual follow-ups outside this PR: install the changesets bot GitHub App, and configure npm trusted publishing for this package (workflow filename: release.yml). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: efe8289 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Summary
Replaces
standard-version(conventional-commits-driven) with Changesets for changelog generation and version bumping..github/workflows/release.ymluseschangesets/actionto open/update a "Version Packages" PR on push tomaster, and auto-publishes to npm on merge.NPM_TOKENsecret, justpermissions: id-token: write. Publishing also gets provenance attestation for free.createGithubReleases: true.@changesets/changelog-github, matching the currentCHANGELOG.mdstyle.docs/intro-to-using-changesets.md: "we recommend not adding a blocking element to contributions in the absence of a changeset"). Relying on the changesets bot (installed separately, see below) for a non-blocking nudge instead.chore(deps)commits don't trigger a release); dropped the now-unused:semanticCommitspreset..github/workflows/lint-pr-title.yml(conventional-commit PR title lint) — no longer functionally needed since changeset files, not commit/PR title format, now drive versioning.minorrather thanmajor— Changesets callssemver.inc()with no 0.x awareness, so amajorchangeset would jump0.10.1straight to1.0.0;minorkeeps the release at0.11.0, consistent with staying in the 0.x range for now.Follow-ups (not in this PR, need manual action)
marking-menuon npmjs.com: orgQuentinRoy, repoMarking-Menu, workflow filenamerelease.yml.Test plan
yarn lint— clean (pre-existing warnings only, unrelated to this change)yarn format:check— cleanyarn coverage— 111 tests passingyarn build-demo— builds successfullyyarn changeset status --verbose— confirms next release proposesmarking-menu@0.11.0🤖 Generated with Claude Code