Repository navigation
chore: migrate to changesets v3 - #541
Merged
Merged
Conversation
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
tuler
force-pushed
the
feat/changeset-v3
branch
from
October 6, 2026 03:59
af6993a to
1d8db08
Compare
tuler
added this pull request to stack #542
October 6, 2026 03:59
tuler
force-pushed
the
feat/changeset-v3
branch
from
October 6, 2026 12:57
1d8db08 to
74550ec
Compare
tuler
force-pushed
the
feat/changeset-v3
branch
from
October 6, 2026 14:22
74550ec to
6ea446e
Compare
tuler
force-pushed
the
feat/changeset-v3
branch
from
October 7, 2026 17:46
6ea446e to
fef6524
Compare
brunomenezes
approved these changes
Oct 7, 2026
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.
Migrates the repo to Changesets v3, following https://changesets.dev/guide/migration.
Changes
@changesets/cli^2.31.1→^3.0.3..changeset/config.json: schema URL bumped to@changesets/config@4.0.1.baseBranchandprivatePackages(version: true, tag: true) were already explicit, so v3's new default of not versioning private packages doesn't affect@cartesi/sdktagging.changeset status. All 285 already-versioned changesets (including those released in2.0.0-alpha.38) moved to.changeset/pre/, andpre.jsonnow only holdsmode/tag. No changesets are pending.release.yaml:changesets/actionv1.9.0 → v2.1.2 (SHA-pinned). Inputs renamed (commit→commit-message,publish→publish-script) and theGITHUB_TOKENenv is dropped (the action defaults togithub.token).publishedPackages→published-packages. The job-level output name is unchanged, sobuild_sdkdidn't need updating.setup-nodepinned to Node 24, because v3 requires^22.11 || ^24 || >=26.bun.lock: the@cartesi/cliworkspace version is synced to2.0.0-alpha.38, which the release commit left stale.publish-packagesscript is now justchangeset publish. Action v2 creates git tags and GitHub releases itself through the API (fromCHANGESETS_OUTPUT), sogit push --follow-tagsis no longer needed.Notes
npm, the same as v2.biome cipasses, and a drychangeset version(run before rebasing onto thealpha.38release) bumped@cartesi/clifrom2.0.0-alpha.37toalpha.38with the expected changelog.🤖 Generated with Claude Code