shell-api 3.13.0 #547
Merged
shell-api 3.13.0 #547
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
Err, it might be worth digging into this deeper ... this should not be happening 🙂 Aside, we're in an awkward situation here because I messed up the last release and 3.13 isn't actually the latest release, 3.12 is (Slack thread). And that should get resolved by the next mongosh release, like, almost immediately, but that is blocked on Evergreen being buggy and not picking up the release (Slack thread) |
addaleax
approved these changes
Jun 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
mongodb-ts-autocomplete now doesn't want to install from shell-api because the peer dep version doesn't match. I guess this will then break again the moment shell-api bumps after merging the PR there..