mongosh 2.5.5

[addaleax]

Not sure what exactly happened here, but this is a re-do of #228956 / #228958 – the replacement PR was merged, but the commit seems to have been force-pushed out of the master and main branches.

So I'm opening a PR here with that commit from a personal fork, so that the bot can force-push to it – I assume there's more to the story, although I couldn't find any references in the issues/PRs in this repo that would clarify this.

[chenrui333]

So I'm opening a PR here with that commit from a personal fork, so that the bot can force-push to it – I assume there's more to the story, although I couldn't find any references in the issues/PRs in this repo that would clarify this.

there is a label for it (no push access)

[chenrui333]

Not sure what exactly happened here, but this is a re-do of #228956 / #228958

it was because of the base branch issue (it should be main rather than master branch)

[addaleax]

@chenrui333 Cool, that's good to know – we'll update our automation to create these PRs against main on release 👍

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.

[github-actions]

⚠️ Bottle publish failed.

[addaleax]

If there's no easy fix for the above (mongosh 2.5.5 bottles already having been built, iiuc), we'll just do another release tomorrow.