-
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 fails to identify latest tag from dependency after default branch changed #5421
Comments
Are you pinning to a tag or a SHA of the tag? Because #5516 may have fixed this. Can you check? |
We are pining by tag. #5516 was merged 14 days ago, so I guess every dependabot run afterwards includes the new logic already, or?
|
It's actually hard to tell. I've a private test repo with multiple workflows using However, when I manually trigger a dependabot check I still get this output
|
I that may be because of #3750? |
I think this are two distinct issues. The one you linked happens when multiple instances with different versions are used and dependabot did not check for updates for the lower/lowest version. |
Oh, ok, I misunderstood that you were actually using Can you try creating a public repository with the same |
I setup a new test repo (https://github.com/yubiuser/dependabot_test) and there everything is working as expected. I have no idea why it is not working in the other....
|
Yeah referencing commits of an incorrect branch should've really been fixed by #6052. However, your sample repo does not pin by sha, right? And you mentioned previously that the problem was pinning by SHA? |
No, we always pin by tag. But as you can see here, it's returning SHA:
|
Sorry, misunderstood again! So you real repository is simply pinning |
Whatever it is, I just noticed that other cases that will be fixed by #5963 are also incorrectly returning a SHA as the current version and not being able to update certain actions. So I'm going to set #5963 to also close this issue, and will make sure to let you know when it's live so you can test again 👍. |
Thanks for letting me know. I'll test again when #5963 is merged. |
No avail.
|
That's too bad. And there are not other places in your configuration files that use |
Ok, ok. Then again this looks like #3750. From all the actions, Dependabot is only considering the first one. And it can't propose any updates for the first one because it's pinned to a branch without any version requirement, makes sense? |
I think you disentangled it! |
Let me close this issue in favor of #3750 then. There's already an open PR for that ticket, so I expect to get that fixed soonish. |
Package ecosystem
github-actions
dependabot.yml content
Updated dependency
uses: actions/[email protected]
What you expected to see, versus what you actually saw
Expect new PR for
actions/[email protected]
Observed: No update needed
Log:
I'm using
dependabot
to updategithub-actions
. One of those is https://github.com/actions/checkout. When specifying an "old" tag (v3.0.0) I expect dependabot to open a PR for the latest v3 versio (v3.0.2). See here for tags: https://github.com/actions/checkout/tags.However,
dependabot
is referencing an "old" commit aslatest version
. This commit is the latest in theirmaster
branch (https://github.com/actions/checkout/commits/master), but they have changed tomain
as their default branch (https://github.com/actions/checkout/commits/main).The text was updated successfully, but these errors were encountered: