Upgrade @changesets/ tooling to latest #1129
Closed
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:
I have been chasing an issue where bumping to a snapshot version sometimes yields and inconsistent set of updates (some snapshotted packages don't reference the snapshot version of a dependency).
For example: In one case I bumped to a snapshot version where
perseus
,perseus-editor
andmath-input
were all modified. As a result,perseus-editor
should be pointing to the snapshot version ofmath-input
. But in the case I encountered, it was pointing to the unchanged, production version.I am bumping changesets to the latest v2.27.1 (see https://github.com/changesets/changesets/releases?q=cli&expanded=true). I think v2.23.1 fixed the issue (see release notes), specifically:
Issue: "none"
Test plan:
git add .
yarn changeset version --snapshot PR0000
git diff
- verify that each package that references a modified dependency is using the snapshot version