feat(release): automate versioning and releases with changesets#60
Open
WilliamBergamin wants to merge 7 commits into
Open
feat(release): automate versioning and releases with changesets#60WilliamBergamin wants to merge 7 commits into
WilliamBergamin wants to merge 7 commits into
Conversation
Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
WilliamBergamin
added
documentation
WilliamBergamin
commented
Jun 29, 2026
Comment on lines
+76
to
+78
| changeset: ## Create a changeset describing a user-facing change (for the next release) | ||
| npx --yes @changesets/cli add | ||
|
|
Contributor
Author
There was a problem hiding this comment.
Should we just document this? 🤔
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
1 participant
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.
What
Automates versioning and releases with Changesets, so maintainers no longer hand-edit version fields or cut releases manually.
How it works
.changeset/describing the change and its semver bump.package.jsonis the version source of truth.scripts/sync_versions.pythen mirrors that version out to.claude-plugin/plugin.jsonand.cursor-plugin/plugin.json.maintriggers.github/workflows/release.yml, which useschangesets/actionto open/update a draft "chore: release" PR, bumps the version, and updates the changelog.npx @changesets/cli publish.Config & conventions
.changeset/config.json: private package (privatePackages: { version, tag }),baseBranch: main, frontmatter key is always"slack".