chore(release): bump package versions #7428
Merged
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]](https://avatars.githubusercontent.com/u/124201131?s=80&v=4){kind=small}
mongodb-devtools-bot
bot
added
bot
no-title-validation
|
Assigned |
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
24 times, most recently
from
9e293fd to
b57e1a4
Compare
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
21 times, most recently
from
ceeebce to
64354cb
Compare
mongodb-devtools-bot
bot
force-pushed
the
ci/bump-packages
branch
from
64354cb to
14b75ba
Compare
johnjackweir
approved these changes
Oct 16, 2025
|
Failing test looks flakey based on task history, I'm gonna go ahead and merge |
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.
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.