-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Support new rangeStrategy=in-range-only #13050
Comments
I'd like to help with this one. |
My plan for fixing this issue:
"update-lockfile = Update the lock file when in-range updates are available, otherwise replace for updates out of range. Works for bundler, composer, npm, yarn, terraform and poetry so far" So, update the For example, for renovate/lib/versioning/composer/index.ts Lines 135 to 145 in 9b2c4b5
renovate/lib/workers/repository/process/lookup/index.ts Lines 164 to 175 in 9b2c4b5
Ensure new range strategy is taken into account here.
renovate/lib/workers/repository/process/lookup/generate.ts Lines 67 to 69 in 9b2c4b5
Ensure new range strategy is taken into account here. |
If rangeStrategy=in-range-only then you need to behave like update-lockfile but discard any updates where newValue !== currentValue. |
I'd be happy to test this out, though I'm not quite sure how to do that. I have an example repository setup where I would want it to function like this. |
🎉 This issue has been resolved in version 31.63.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Hmm, so this feature appears to not update everything "in range". I have the following in my "johnpbloch/wordpress": "~5.5.0",
"johnpbloch/wordpress-core": "~5.5.0", The current version in the lockfile is "johnpbloch/wordpress": "5.5.1",
"johnpbloch/wordpress-core": "5.5.1", And the latest version of 5.5.x is 5.5.8 which will update when I issue a standard - Upgrading johnpbloch/wordpress (5.5.1 => 5.5.8)
- Upgrading johnpbloch/wordpress-core (5.5.1 => 5.5.8) With the setup of using |
What would you like Renovate to be able to do?
Some people prefer to leave the package file unchanged and only do update-lockfile within the existing range.
If you have any ideas on how this should be implemented, please tell us here.
The results should essentially be like
update-lockfile
but discard any updates which need a change to the package file.We should recommend against it in our documentation though, because it means people might end up multiple releases behind without knowing it.
Is this a feature you are interested in implementing yourself?
No
The text was updated successfully, but these errors were encountered: