-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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(datasource): support range constraints filtering #20217
Conversation
I don't see the Blocked by #19979 (i.e. waiting for v35, or could be combined with it) |
@Lctrs this PR is looking good. Do you have any public repos you've been testing against? |
@rarkins no. I trusted the test suite. How can I do that ? |
@Lctrs just have some public repos on github.com which achieve what you're after. For example it could be a Node.js upgrade where the new version requires Node 18 but the project supports 16 and 18, or something similar with python or PHP versions. |
So, I've been able to make it work on a composer project with the last commit. On https://github.com/Lctrs/php-library-skeleton which runs against the official renovate app, renovate opens this update PR which contains an invalid update for On a forked repo, I've got this PR https://github.com/Lctrs/playground/pull/2 which does not contain the invalid update. |
Changes `rangeStrategy` default value from `'replace'` to `'auto'`. Changes `auto` behavior so that `update-lockfile` is preferred if the manager supports the `updateLockedDependency()` function. Closes #19800 BREAKING CHANGE: Renovate will now default to updating locked dependency versions. To revert to previous behavior, configure rangeStrategy=replace.
Set default GOPROXY value to match `go`'s own default. Closes #20040 BREAKING CHANGE: Renovate will now use go's default `GOPROXY` settings. To avoid using the public proxy, configure `GOPROXY=direct`.
Checks file cache for expired items at the end of a run. Non-breaking change but it may result in some long cleanup jobs for any bots which have been left to populate their package cache for a long time. Closes #13732
Co-authored-by: HonkingGoose <[email protected]>
…git tag, and preserve existing digest semantics as separate datasource (#20178) Co-authored-by: RahulGautamSingh <[email protected]> Co-authored-by: Rhys Arkins <[email protected]> Co-authored-by: Michael Kriese <[email protected]> Co-authored-by: HonkingGoose <[email protected]>
This feature is not itself breaking, but it relies on a breaking change in v35.0.0. Should we include it in v35.0.0 or merge it as v35.1.0 after? |
If I have any saying in this decision, I would say ship it ASAP as it's ready. |
It would only be a difference of a few hours at most, once v35 is released |
@rarkins It's up to you :) |
491f0eb
to
a6bbf93
Compare
181a4d7
to
a4ab452
Compare
@rarkins Should I reopen it against main branch ? |
I didn't close it intentionally, sorry. Seems it was closed as a result of v35 getting merged and deleted. Please restore it and retarget towards |
Can't do it by myself. I can't reopen the PR and retarget the branch. But I've rebased my branch on top of main on my fork. |
Can you open a new PR? |
Done #20842 |
Changes
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: