chore: bump version to 1.7.2#72
Open
sverdlov93 wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Syncs
package.json/package-lock.jsonto 1.7.2 to match the published v1.7.2 release.The release workflow normally commits this bump to
main, but it failed becausemainnow requires changes to go through a PR (the workflow pushes the bump commit + floating tags atomically, so the rejectedmainpush also blocked the tag updates). Thev1/v1.7/v1.7.2/v1-node20tags have already been moved manually to the fix commit; this PR just lands the cosmetic version bump onmain.Follow-up: the release workflow should be updated to work under branch protection (see #71 area / release.yml).