Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(maven): Correct order for versions with different length #13552

Merged
merged 6 commits into from Jan 14, 2022

Conversation

zharinov
Copy link
Collaborator

@zharinov zharinov commented Jan 14, 2022

Changes:

Context:

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@rarkins rarkins enabled auto-merge (squash) January 14, 2022 06:27
@rarkins rarkins merged commit 68dfc27 into renovatebot:main Jan 14, 2022
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 31.24.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@zharinov zharinov deleted the fix/maven-versioning-ordering branch January 14, 2022 07:43
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Maven versioning sorting of fix releases Renovate cycles patch upgrades for v2.0, v2.0.SP1 and v2.0-PFD2
3 participants