-
Notifications
You must be signed in to change notification settings - Fork 418
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 update actions/labeler v4.0.2 to 4.1.0 #490
Comments
hi @hhelmken, thank you for the report we will take a look at it. |
hi @hhelmken, yeah that seems weird, can you maybe provide the run that led to this behavior? |
hi @panticmilos, I created a reproduction repository: https://github.com/hhelmken/action-labeler-dependabot/pull/1 |
hi @hhelmken, I am maybe missing something but the commit SHA actually points to the release commit of version I will close this issue for now, but if I missed something feel free to ping me or reopen it :) |
We just had the same happen; 4.1.0 doesn't exist as a release or tag, just as a branch, though? |
Just to follow up on this, 4.1.0 doesn't seem to be a GitHub release or Git tag; it's a branch associated with a closed PR (#421), and also the message on the only commit in that branch. Both are from August 2022, and look like the should maybe deleted to avoid confusing dependabot? |
Description:
In our repository we use Dependabot to update our GitHub Actions. Dependabot created a pull request for updating this action from v4.0.2 to 4.1.0. With this change GitHub Action prints this log output while downloading the action:
Download action repository 'actions/labeler@4.1.0' (SHA:ee18d5d34efd9b4f7dafdb0e363cb688eb438044)
This commit sha is referring to this commit. Do you have any idea what is going on here? I'm not sure if this is an issue of this action or Dependabot itself.
Platform:
Runner type:
Repro steps:
Use this action and configure Dependabot to update GitHub Actions.
The text was updated successfully, but these errors were encountered: