Skip to content

Always let Dependabot propose Cargo.lock updates #58

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

Merged
merged 1 commit into from
Apr 25, 2025

Conversation

EliahKagan
Copy link
Member

@EliahKagan EliahKagan commented Apr 25, 2025

This fixes a bug in the dependabot.yml configuration since #52, where we intend Dependabot to include the effect of cargo update, but this does not happen because dependency-type: all was not explicitly allowed.

This does not make an analogous change to the Dependabot configuration for GitHub Actions, because all and direct currently have the same effect for them (and it is not obvious how it would work if that ever changes, or which we would prefer).

For details on why this is needed for Dependabot to update most locked dependencies in Cargo.lock aside from the case where the update is done as part of updating a Cargo.toml dependency, see:


The corresponding PR in gitoxide (where GitoxideLabs/gitoxide#1948 had the same bug as #52) is GitoxideLabs/gitoxide#1967. The description there contains some information applicable both there and here. The fork-internal Dependabot test PR used to validate this was EliahKagan#8.

The Dependabot PR that will be created due to this changed configuration will include an attempt to upgrade pulldown-cmark. Per #54, that will not currently work. Unless work on that is to proceed soon, it may make sense to have Dependabot automatically ignore non-patch updates to pulldown-cmark. I might make that change separately, but I haven't attempted to include such a thing here; instead, this PR is only for fixing a specific bug in the configuration I added in #52.

This fixes a bug in the `dependabot.yml` configuration since GitoxideLabs#52,
where we intend Dependabot to include the effect of `cargo update`,
but this does not happen because `dependency-type: all` was not
explicitly allowed.

This does not make an analogous change to the Dependabot
configuration for GitHub Actions, because `all` and `direct`
currently have the same effect for them (and it is not obvious how
it would work if that ever changes, or which we would prefer).

For details on why this is needed for Dependabot to update most
locked dependencies in `Cargo.lock` aside from the case where the
update is done as part of updating a `Cargo.toml` dependency, see:

- https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/controlling-dependencies-updated#allowing-specific-dependencies-to-be-updated
- https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference#dependency-type-allow
@EliahKagan EliahKagan marked this pull request as ready for review April 25, 2025 13:59
@EliahKagan EliahKagan merged commit bd30507 into GitoxideLabs:main Apr 25, 2025
9 checks passed
@EliahKagan EliahKagan deleted the dependency-type branch April 25, 2025 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant