POSTRELEASE @W-22462048@ Merging after ecosystem release - #493
Merged
Conversation
|
Git2Gus App is installed but the |
aruntyagiTutu
approved these changes
Jul 28, 2026
aruntyagiTutu
left a comment
aruntyagiTutu
left a comment
Contributor
There was a problem hiding this comment.
Automated SNAPSHOT to release version bump for all 10 core packages, consistent with the versions from #492, lockfile included. No logic changes. Approving.
nikhil-mittal-165
changed the title
Contributor
|
approved |
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
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.
This branch and PR were automatically created as part of a Package Publish.
The branch increments the .version property of published packages from X.Y.Z-SNAPSHOT to X.Y.Z, and updates anyinter-package dependencies appropriately.
The narrow scope of these changes makes a merge conflict unlikely, but if one does occur, you should consultwith the author of the conflicting change and decide what to do next. Ultimately it may make sense to not mergethis pull request at all. Use your judgment.