Fix renovate integaration #1261
Merged
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
At least when using the PEP621 backend (uv), renovate only cares about
dependencies which have at least one constraint, otherwise it bypasses
them.
This can see from the logs:
{
"datasource": "pypi",
"depName": "pyzstd",
"depType": "project.dependencies",
"lockedVersion": "0.17.0",
"packageName": "pyzstd",
"skipReason": "unspecified-version",
"updates": []
},
https://developer.mend.io/github/onekey-sec/unblob
…ed in uv.lock Since some time around April, renovate started to update only packages, where `pyproject.toml` update was needed (constraints update). I have not found documentation about this change, only a github discussion[^1]. Meaning of rangeStrategy=update-lockfile[^2] option: > Update the lock file when in-range updates are available, otherwise > replace for updates out of range. And replace: > Replace the range with a newer one if the new version falls outside > it, and update nothing otherwise [^1]: renovatebot/renovate#36286 [^2]: https://docs.renovatebot.com/configuration-options/#rangestrategy
kukovecz
approved these changes
Sep 19, 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.
Since some time around April, renovate started to update only
packages, where
pyproject.tomlupdate was needed (constraintsupdate).
I have not found documentation about this change, only a github discussion1.
Meaning of rangeStrategy=update-lockfile2 option:
And replace:
At least when using the PEP621 backend (uv), renovate only cares about
dependencies which have at least one constraint, otherwise it bypasses
them.
This can see from the logs3:
Footnotes
https://github.com/renovatebot/renovate/discussions/36286 ↩
https://docs.renovatebot.com/configuration-options/#rangestrategy ↩
https://developer.mend.io/github/onekey-sec/unblob ↩