You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have different granularity of our dependency versions across different Cargo.toml files, but also in single files.
Some examples: plugins/priority/Cargo.toml: serde-aux = "4" collectors/slurm/Cargo.toml: serde-aux = "4.2.0" collectors/slurm/Cargo.toml: anyhow = "1"
Should this be harmonized?
If we just use the major version, we have less work with dependabot PRs. But in our current workflow, we only get the minor version updates when we run cargo update before releasing a new AUDITOR version.
If we use the minor version, we get regular dependabot PRs and workflow checks during the development.
The text was updated successfully, but these errors were encountered:
dirksammel
changed the title
Harmonize granularity of dependency version?
Harmonize granularity of dependency versions?
Nov 23, 2023
We currently have different granularity of our dependency versions across different
Cargo.toml
files, but also in single files.Some examples:
plugins/priority/Cargo.toml
:serde-aux = "4"
collectors/slurm/Cargo.toml
:serde-aux = "4.2.0"
collectors/slurm/Cargo.toml
:anyhow = "1"
Should this be harmonized?
If we just use the major version, we have less work with
dependabot
PRs. But in our current workflow, we only get the minor version updates when we runcargo update
before releasing a new AUDITOR version.If we use the minor version, we get regular
dependabot
PRs and workflow checks during the development.The text was updated successfully, but these errors were encountered: