Modify Renovate configuration for improved management - #40
Merged
Merged
Conversation
Updated Renovate configuration to include new settings and remove deprecated ones.
Coverage Report for CI Build 35222891391Warning No base build found for commit Coverage: 86.202%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
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
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.
Summary
This change should set up renovate to properly deal with dependencies in a python project managed by actions.
Changes
Impact
The impact of this is that we will have renovate properly set up to version deps using a widen strategy which is more like what a project like this should have. Since this code is often installed next to other codes we need wider support for more sw versions, not just tracking latest. This will also fix the in-range strategy not matching any updates when a range is supplied in the project toml that tightly limits updates to ranges that enclose the range to lower than newer releases.