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
Manifest location and content before the Dependabot update
I have a cargo workspace with one crate. I also have a crate that is explicitly not part of the workspace. The crate outside of the workspace has a path-dependency to the crate in the workspace.
crate-in-workspace depends on the crate rustix. This is an arbitrary dependency, I tried multiple different ones, it does not matter which dependency it is nor which version number it is. The bug occurs when any dependency of crate-in-workspace is updated by Dependabot.
What you expected to see, versus what you actually saw
I expected crate-outside-workspace's Cargo.lock file to be updated in this PR, since the crate depends on a crate-in-workspace, whose dependency got updated. This did not happen.
Native package manager behavior
I only know of manually updating Cargo.toml, so unsure how major versions are usually automatically updated.
Images of the diff or a link to the PR, issue, or logs
As you can see in this PR, CI fails, because crate-outside-workspace's Cargo.lock file was not updated, when it should have been.
Is there an existing issue for this?
Package ecosystem
Cargo
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
I have a cargo workspace with one crate. I also have a crate that is explicitly not part of the workspace. The crate outside of the workspace has a path-dependency to the crate in the workspace.
Please see files at https://github.com/ludfjig/dependabot-test-repo
dependabot.yml content
also available at https://github.com/ludfjig/dependabot-test-repo
Updated dependency
crate-in-workspace
depends on the craterustix
. This is an arbitrary dependency, I tried multiple different ones, it does not matter which dependency it is nor which version number it is. The bug occurs when any dependency ofcrate-in-workspace
is updated by Dependabot.What you expected to see, versus what you actually saw
I expected
crate-outside-workspace
'sCargo.lock
file to be updated in this PR, since the crate depends on acrate-in-workspace
, whose dependency got updated. This did not happen.Native package manager behavior
I only know of manually updating
Cargo.toml
, so unsure how major versions are usually automatically updated.Images of the diff or a link to the PR, issue, or logs
As you can see in this PR, CI fails, because
crate-outside-workspace
'sCargo.lock
file was not updated, when it should have been.Smallest manifest that reproduces the issue
See above yml. I have a repro at ludfjig/dependabot-test-repo#4
The text was updated successfully, but these errors were encountered: