Run yarn bump-versions on the last set of changes that made it to npm
#3928
Conversation
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
Saadnajmi
approved these changes
Jul 10, 2025
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.
The step of committing the local bump version to the repo has been broken. This then breaks the publish steps because npm thinks we're trying to republish to an existing version. The step which commits the version bump to the repo should be fixed now, so we need to get the publishing pipeline back on track.
This change runs beachball's bump against the last change that made it to NPM, which was #3896. This makes sure the Changelog and set of packages to update are correct when we run publish the next time.
Change files left over are for changes that have not reached npm yet. When this PR gets approved, the publish pipeline should then publish all outstanding changes since the last change that reached npm, and then update all the local packages accordingly.
The change files for this change are
noneas they shouldn't affect the package itself (otherwise we get in an infinite loop)