Skip to content
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

Add update types for Cargo-style (in)compatible version upgrades #9681

Open
1 task done
jwodder opened this issue May 6, 2024 · 0 comments
Open
1 task done

Add update types for Cargo-style (in)compatible version upgrades #9681

jwodder opened this issue May 6, 2024 · 0 comments
Labels
L: go:modules Golang modules L: rust:cargo Rust crates via cargo T: feature-request Requests for new features

Comments

@jwodder
Copy link

jwodder commented May 6, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

Currently, the only options for update-types in dependabot.yml are "major", "minor", and "patch", all defined as per SemVer. However, Cargo (the Rust package manager) uses a modified form of SemVer in which "Versions are considered compatible if their left-most non-zero major/minor/patch component is the same." Thus, a version upgrade from v0.1.0 to v0.2.0 is considered "incompatible" even though, by typical SemVer standards, it is minor.

I therefore request that ignore.update-types and groups.*.update-types gain support for the options cargo-compatible and cargo-incompatible (just spitballing on the names) for ignoring/grouping (in)compatible version updates.

@jwodder jwodder added the T: feature-request Requests for new features label May 6, 2024
@github-actions github-actions bot added L: go:modules Golang modules L: rust:cargo Rust crates via cargo labels May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: go:modules Golang modules L: rust:cargo Rust crates via cargo T: feature-request Requests for new features
Projects
Status: No status
Development

No branches or pull requests

1 participant