-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Dependabot opened a PR to update one dependency, but also downgraded another dependency. #5757
Comments
Is this the same as #4536? Can you try to reproduce it locally using the instruction here? #4536 (comment) I'd love to see this one fixed, it was super annoying at my last job before I joined the Dependabot team, but the number of users impacted is relatively low so just haven't gotten to it yet. |
I got very similar results from both sets of commands. go 1.18 here.
output (trimmed to relevant parts)
Second set of commands:
|
I am seeing similar issues. PR for ref |
Hey there! 👋 We are also seeing this issue on grafana/clickhouse-datasource#447, the |
Had another occurrence of this issue, this time when the |
If I clone https://github.com/grafana/clickhouse-datasource and run
So it seems the upgrade bumped the indirect dependency However, Dependabot also runs a bare go get, which fixes the broken state by downgrading clickhouse-go (probably using minimum version selection). I suspect this is the source of all the downgraded dependencies. If anyone else wants to confirm by running the above steps on their repo that would help! |
Is there an existing issue for this?
Package ecosystem
go
Package manager version
No response
Language version
1.18
Manifest location and content before the Dependabot update
dependabot.yml content
Updated dependency
github.com/shipt/tempest v1.10.6 -> github.com/shipt/tempest v1.10.7
What you expected to see, versus what you actually saw
This PR, named
Bump github.com/shipt/tempest from 1.10.6 to 1.10.7
not only bumped Tempest, but it downgradedgithub.com/shipt/pipeline-manager
fromv0.53.8
tov0.24.1
expected:
got:
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: