Skip to content
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

Closed
evgeni opened this issue Jul 9, 2020 · 2 comments · Fixed by #5891
Closed

Allow bumping GH actions to rolling releases #2304

evgeni opened this issue Jul 9, 2020 · 2 comments · Fixed by #5891
Labels
core 🍏 Relates to the dependabot-core library itself L: github:actions GitHub Actions T: feature-request Requests for new features

Comments

@evgeni
Copy link

evgeni commented Jul 9, 2020

Currently dependabot will bump GitHub actions to whatever the latest vX.Y.Z tag is. However, actions also usually have a vX tag that points to the latest X.Y.Z (and gets updated). I'd like to be able to select the bumping behavior and prefer vX tags.

Example PR that was opened with full version and then manually changed to v2: theforeman/releasetool#19

@evgeni
Copy link
Author

evgeni commented Jul 9, 2020

cc @ekohl

@jurre 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
@nickserv
Copy link

nickserv commented Jun 22, 2022

I've noticed this is also an issue when the same major version tag has an update. For example, v2 should not be bumped to v2.0.1.

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.

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants