Renovate 44 was accidentally released as a major version (with a non-breaking change) #44952
jamietanna
announced in
Maintainer announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Renovate 44.0.0 was incorrectly released from #44004 due to the
BREAKING CHANGEreference in the commit message.To be very clear - the changes in 44.0.0 are not breaking changes.
Renovate uses Squash Merge as our method for merging commits into
main, and when enabled with the Merge Queue[0], this doesn't provide maintainers with the ability to inspect the commit messages before merging (which would be the case if not using the Merge Queue, we would likely rewrite the commit message prior to merge.With this in mind, Renovate maintainers often don't inspect the commit messages, allowing them to stay as they are, as they'll be squashed into the final commit.
In the case of #44004, this led to us missing the
BREAKING CHANGEtrailing message - from changes that were split into #44939 - and because of this,semantic-releasepublished this as a major release.We've since added a CI check in #44944 to catch this, but in the meantime, we're treating Renovate 44 as if it was a continuation of Renovate 43, and not as a breaking change.
Apologies in advance!
All reactions