ci: automate versioning and releases with changesets by WilliamBergamin · Pull Request #60 · slackapi/slack-mcp-plugin

WilliamBergamin · 2026-06-23T20:18:18Z

What

Automates versioning and releases with Changesets, so maintainers no longer hand-edit version fields or cut releases manually.

How it works

Contributors add a changeset for user-facing changes with a markdown file in .changeset/ describing the change and its semver bump.
package.json is the version source of truth.
- Changesets bumps it
- scripts/sync_versions.py then mirrors that version out to .claude-plugin/plugin.json and .cursor-plugin/plugin.json.
Merging changesets to main triggers .github/workflows/release.yml, which uses changesets/action to open/update a draft "chore: release" PR, bumps the version, and updates the changelog.
Merging that release PR publishes the release via npx @changesets/cli publish.

Config & conventions

.changeset/config.json: private package (privatePackages: { version, tag }), baseBranch: main, frontmatter key is always "slack".

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>

WilliamBergamin · 2026-06-29T16:01:27Z

+changeset: ## Create a changeset describing a user-facing change (for the next release)
+	npx --yes @changesets/cli add
+


Should we just document this? 🤔

🔭 thought: Recent commits for contributors guide and this "help" command seem solid to me!

$ make help changeset Create a changeset describing a user-facing change (for the next release)

zimeg

@WilliamBergamin Amazing changes to see! 🚀 ✨

I'm leaving a few comments and thoughts but might call out locking dependencies as part of this project? I understand it adds more node to a python project but the added confidence in releases is what motivates me.

Please feel free to merge whenever though! All changes are great! I was quibbling in review 👻

zimeg · 2026-06-24T06:39:59Z

 [gh-cli]: https://cli.github.com
 [conv-commits]: https://www.conventionalcommits.org
 [semver]: https://semver.org
+[changesets]: https://github.com/changesets/changesets


Suggested change

[changesets]: https://github.com/changesets/changesets

🪓 quibble(non-blocking): Is this link inlined instead?

zimeg · 2026-06-30T09:01:11Z

+
+1. **Run the tests locally**: Before merging the release PR please run all the tests especially the eval ones. If they no longer pass we may need fix it before releasing the changes.
+
+2. **Check GitHub**: Please check if issues or pull requests are still open either decide to postpone the release or save those changes for a future update.


🔮 question: Are milestones something we want to introduce here, either now or later?

zimeg · 2026-06-30T09:06:49Z

+
+3. **Review the release PR**: Verify that the version bump matches expectations, `CHANGELOG` entries are clear, and CI checks pass.
+
+4. **Merge and approve**: Merge the release PR. It may take up to 24 hours before you see you release in [plugins/slack](https://claude.com/plugins/slack).


Suggested change

4. **Merge and approve**: Merge the release PR. It may take up to 24 hours before you see you release in [plugins/slack](https://claude.com/plugins/slack).

4. **Merge and approve**: Merge the release PR. It may take up to 24 hours before you see you release in the [Claude Plugins](https://claude.com/plugins/slack) directory.

🦠 suggestion: This wording might be odd but I based it from the backing project.

Claude Code Plugins Directory

🔗 https://github.com/anthropics/claude-plugins-official

zimeg · 2026-06-30T09:12:46Z

+Add the channel-digest command
+```
+
+The frontmatter key is always `"slack"`, the value is the [semver](https://semver.org/) bump level. The body becomes the changelog entry, so write it for a reader of the release notes.


Suggested change

The frontmatter key is always `"slack"`, the value is the [semver](https://semver.org/) bump level. The body becomes the changelog entry, so write it for a reader of the release notes.

The frontmatter key is always `"slack"`, the value is the [semver](https://semver.org/) bump level - `patch`, `minor`, or `major`. The body becomes the changelog entry, so write it for a reader of the release notes.

📚 suggestion(non-blocking): For quick reads wanting example these versions might be nice?

zimeg · 2026-06-30T09:19:20Z

+    steps:
+      - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+        with:
+          fetch-depth: 0


Suggested change

fetch-depth: 0

fetch-depth: 0

persist-credentials: false

🔏 suggestion: To avoid oddities with actions later-

zimeg · 2026-06-30T09:28:47Z

+changeset: ## Create a changeset describing a user-facing change (for the next release)
+	npx --yes @changesets/cli add
+


🔭 thought: Recent commits for contributors guide and this "help" command seem solid to me!

$ make help changeset Create a changeset describing a user-facing change (for the next release)

zimeg · 2026-06-30T09:34:14Z

🎁 suggestion: I think we should include the @changeset/cli package here alongside a lockfile to avoid surprise in updates. IIRC "v3" is in development at the moment!

🍰 ramble: I'm not wanting to add separate documentation for this either! I'm curious if the scripts/changeset_version.sh file and make file might just... re-install the packages? This might be upsetting.

zimeg · 2026-06-30T09:43:45Z

+    """Set the ``version`` field of a JSON plugin manifest."""
+    manifest = json.loads(plugin_path.read_text())
+    manifest["version"] = version


👁️‍🗨️ thought: I'm curious if separate functions for different targets might improve maintenance but not a blocker whatsoever-

zimeg · 2026-06-30T09:46:03Z

🌟 praise: Great to see these scripts extended so well!

zimeg · 2026-06-30T09:51:33Z

+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": [],
+  "privatePackages": { "version": true, "tag": true }


🧮 quibble: A small preference to linebreaks for each argument to avoid missed details when scrolling. But not blocker of course.

WilliamBergamin and others added 6 commits June 23, 2026 11:30

feat(release): automate versioning and releases with changesets

023e91b

chore(release): replace new_changeset.py with npx @changesets/cli add

de7cce9

update

cc9845b

use package.json

eb2f10a

Update AGENTS.md

bd3f325

chore(release): drop unused import in sync_versions.py

ce0edf6

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>

WilliamBergamin requested a review from mwbrooks June 23, 2026 20:25

WilliamBergamin self-assigned this Jun 23, 2026

WilliamBergamin requested a review from zimeg June 23, 2026 20:25

WilliamBergamin added documentation Improvements or additions to documentation release changes are related to releases labels Jun 23, 2026

WilliamBergamin marked this pull request as ready for review June 23, 2026 20:27

Merge branch 'main' into release-process

31c18f0

WilliamBergamin commented Jun 29, 2026

View reviewed changes

zimeg changed the title ~~feat(release): automate versioning and releases with changesets~~ ci: automate versioning and releases with changesets Jun 30, 2026

zimeg approved these changes Jun 30, 2026

View reviewed changes

		changeset: ## Create a changeset describing a user-facing change (for the next release)
		npx --yes @changesets/cli add


		1. Run the tests locally: Before merging the release PR please run all the tests especially the eval ones. If they no longer pass we may need fix it before releasing the changes.

		2. Check GitHub: Please check if issues or pull requests are still open either decide to postpone the release or save those changes for a future update.


		3. Review the release PR: Verify that the version bump matches expectations, `CHANGELOG` entries are clear, and CI checks pass.

		4. Merge and approve: Merge the release PR. It may take up to 24 hours before you see you release in [plugins/slack](https://claude.com/plugins/slack).

	The frontmatter key is always `"slack"`, the value is the [semver](https://semver.org/) bump level. The body becomes the changelog entry, so write it for a reader of the release notes.
	The frontmatter key is always `"slack"`, the value is the [semver](https://semver.org/) bump level - `patch`, `minor`, or `major`. The body becomes the changelog entry, so write it for a reader of the release notes.

Uh oh!

Conversation

WilliamBergamin commented Jun 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

How it works

Config & conventions

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

zimeg left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

WilliamBergamin commented Jun 23, 2026 •

edited

Loading