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.
The interesting part to review here is scripts/npm-package-release.sh which replaces the old
new-release-*scripts. I did my best to make it idempotent and foolproof.The rest is all automatic changes performed by
yarn changeset.Note that I think ideally this change would be pushed without squashing to preserve the commit hash, but I don't have permissions to bypass the merge queue on main. I'm not sure it actually matters when I'm skipping the git tagging part of the publish workflow. For reproducibility, we certainly wouldn't want other PRs to land on main before this one, which would confuse the question of what was in a given release.