chore(release): bump package versions #7232
Merged
+2,124
−2,124
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
mongodb-devtools-bot
bot
added
the
no-title-validation
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
28 times, most recently
from
a980f24 to
d1b4d25
Compare
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
14 times, most recently
from
eab1546 to
ebbfda6
Compare
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
10 times, most recently
from
abd6923 to
be4a573
Compare
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
from
be4a573 to
3005c7f
Compare
lerouxb
approved these changes
Sep 4, 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.
This PR is autogenerated and updates the version of every package in the monorepo that was changed since last publish. If you need to publish packages to update the version elsewhere, you can do this at your own convenience by just merging this PR.
After PR is merged, it starts an automatic publish process via GitHub Actions, you can follow the process on the publish workflow page.