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

feat(versioning/gradle): Support maven ranges in gradle files #26846

Merged
merged 2 commits into from Jan 29, 2024

Conversation

Kouzukii
Copy link
Contributor

@Kouzukii Kouzukii commented Jan 24, 2024

Changes

Maven version ranges like [1.2.3,2) are supported by gradle.
Renovate handles these correctly for maven projects, for gradle projects however it does not create an update.
With this PR gradle version ranges will get updated just like maven's do.

Context

We heavily use maven version ranges in our gradle projects and were surprised these were not updated by renovate.

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 select 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 added this pull request to the merge queue Jan 29, 2024
Merged via the queue into renovatebot:main with commit 0841444 Jan 29, 2024
36 checks passed
@rarkins
Copy link
Collaborator

rarkins commented Jan 29, 2024

Thanks @Kouzukii for your PR!

@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.155.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

rvanbutselaar pushed a commit to rvanbutselaar/renovate that referenced this pull request Feb 2, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2024
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.

None yet

3 participants