-
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
Allow bumping GH actions to rolling releases #2304
Labels
core 🍏
Relates to the dependabot-core library itself
L: github:actions
GitHub Actions
T: feature-request
Requests for new features
Comments
cc @ekohl |
This was referenced Feb 7, 2021
This was referenced Feb 8, 2021
This was referenced Feb 8, 2021
This was referenced Feb 16, 2021
This was referenced May 25, 2021
Closed
jurre
added
L: github:actions
GitHub Actions
T: feature-request
Requests for new features
core 🍏
Relates to the dependabot-core library itself
labels
Dec 1, 2021
I've noticed this is also an issue when the same major version tag has an update. For example, I think we should respect the existing tag precision to stay consistent with #4953. GitHub Actions docs tend to use major version tags anyway, so this should still simplify Dependabot usage for those users. |
This was referenced Jun 22, 2022
1 task
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
core 🍏
Relates to the dependabot-core library itself
L: github:actions
GitHub Actions
T: feature-request
Requests for new features
Currently dependabot will bump GitHub actions to whatever the latest
vX.Y.Z
tag is. However, actions also usually have avX
tag that points to the latest X.Y.Z (and gets updated). I'd like to be able to select the bumping behavior and prefervX
tags.Example PR that was opened with full version and then manually changed to
v2
: theforeman/releasetool#19The text was updated successfully, but these errors were encountered: