Repository navigation
Drop Dependabot's versioning strategy for cargo - #75
Merged
Merged
Conversation
For cargo, Dependabot accepts only `auto` and `lockfile-only` as a versioning strategy, so it rejected the config's `increase`, and since #74 its `increase-if-necessary`, and ran no updates. `auto`, the default, already does what `increase-if-necessary` meant to: it updates Cargo.lock, and raises a requirement in Cargo.toml only for a release that the requirement doesn't allow.
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
1 participant
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
.github/dependabot.ymlsince Warn about files that don't parse, read<%==in ERB, and release 0.7.0 #72, so it has run no updates. For cargo it accepts onlyautoandlockfile-onlyas aversioning-strategy. Warn about files that don't parse, read<%==in ERB, and release 0.7.0 #72'sincreasefailed with "did not match one of the following values: lockfile-only, auto", and Commit Cargo.lock #74'sincrease-if-necessaryfails the same way (check on main).BumpVersionsIfNecessary(source). It updatesCargo.lock, and raises a requirement inCargo.tomlonly for a release that the requirement doesn't allow, which is what Commit Cargo.lock #74 meant to choose.Test plan
check-jsonschema --builtin-schema vendor.dependabot). That schema doesn't encode cargo's two values, though: it passes the file on main too.