fix(ci): use the correct commit message when bumping packages MONGOSH-1871 #2333
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
bump-packages from monorepo-tools is looking for chore(ci): bump packages as the start of the commit to calculate the semver bump. The problem is that our commit message doesn't start with this - instead it's chore(release): bump auxiliary packages. This means that the next time we run it, we go back to the start of time and sure enough, we find some breaking: ... commit message and decide we need to bump major. Luckily there's a LAST_BUMP_COMMIT_MESSAGE we can use to set this.
gagik
added
the
no-title-validation
gagik
removed
the
no-title-validation
gagik
changed the title
nirinchev
approved these changes
Jan 28, 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.
bump-packages from monorepo-tools is looking for
chore(ci): bump packagesas the start of the commit to calculate the semver bump. The problem is that our commit message doesn't start with this - instead it'schore(release): bump auxiliary packages. This means that the next time we run it, we go back to the start of time and sure enough, we find some breaking: ... commit message and decide we need to bump major. Luckily there's aLAST_BUMP_COMMIT_MESSAGEwe can use to set this, so this does that.