ci: publish GitHub Releases from changesets release step#71
Merged
Conversation
Enable createGithubReleases on changesets/action so each `slack@<version>` tag gets a populated release page (using the auto-generated notes template already in .github/release.yml). This gives release links something real to point at ahead of automating the Slack release announcement.
mwbrooks
added
semver:patch
mwbrooks
changed the title
WilliamBergamin
approved these changes
Jul 2, 2026
WilliamBergamin
left a comment
WilliamBergamin
left a comment
Contributor
There was a problem hiding this comment.
Nice catch 💯 thanks for opening a PR for this 🚀
Member
Author
|
@WilliamBergamin No problem, I only noticed while working on another PR. I figured it would be easier to break this out for an easy review. Thanks for the eyes 👀 |
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
2 participants
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
This pull request create a GitHub Release in our release action:
createGithubReleases: trueto thechangesets/actionstep in.github/workflows/release.ymlso eachslack@<version>tag lands on a populated GitHub Release page, using the auto-generated notes template already staged in.github/release.yml. No new permissions needed — the job already hascontents: write.Preview
Testing
make lintlocally - passes.Changesets releasestep should succeed with no permissions errors, andhttps://github.com/slackapi/slack-mcp-plugin/releases/tag/slack@<version>should render a populated release with categorized notes from.github/release.yml, rather than the empty tag page we get today.Notes
testlabel until we have a proper label for this type of work.Requirements
make testand the tests pass.