ci: migrate release workflow to changesets/action v2 and Changesets CLI v3 - #182
Merged
MattiasBuelens merged 2 commits intoSep 3, 2026
Merged
Conversation
Co-Authored-By: Mattias Buelens <mattias.buelens@dolby.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
Co-Authored-By: Mattias Buelens <mattias.buelens@dolby.com>
MattiasBuelens
deleted the
devin/1788467409-changesets-action-v2-inputs
branch
September 3, 2026 20:38
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
#179 bumped
changesets/actionto 2.1.1, but the release workflow still used the v1 inputs and the repo still used Changesets CLI v2. The first release run after the bump failed with:This PR makes the workflow compatible with action v2:
release.ymlGITHUB_TOKENenv var is no longer read by the action. The app token is now passed through thegithub-tokeninput. Without it, the action falls back togithub.tokenand the release commits/PR are not attributed totheoplayer-bot.commit→commit-message,title→pr-title,version→version-script,publish→publish-script,createGithubReleases→create-github-releases.# v1version comment on the pinned SHA to# v2.1.1. Dependabot only rewrites this comment when it ends with a tag that points to the old SHA;changesets/actionpublishes no major tags (v1,v2), so# v1was never updated.Changesets CLI v3
@changesets/cli^2.31.0→^3.0.1,@changesets/types^6.1.0→^7.0.0, config$schema→@changesets/config@4.0.0..changeset/format.mjschangelog module andpost-process.mjsstill work:npm run changeset:versionlocally bumps both fixed packages to 2.3.3 and produces the expected### 🐛 Issues/### 📦 Dependency Updatessections.Note: action v2 pushes release commits and tags through the GitHub API by default (signed, attributed to the app that owns
github-token), so the "Configure Git user" step is no longer needed for the release commit. It is left in place as it is harmless.Link to Devin session: https://dolby.devinenterprise.com/sessions/09ce8fec2c0c42ea89616f48717fb546
Open in Devin Desktop: https://dolby.devinenterprise.com/desktop/session/09ce8fec2c0c42ea89616f48717fb546?variant=devin
Requested by: @MattiasBuelens