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

Use dependabot for simplifying GitHub actions version management #27816

Closed
marcwrobel opened this issue Sep 8, 2022 · 1 comment · Fixed by #27830
Closed

Use dependabot for simplifying GitHub actions version management #27816

marcwrobel opened this issue Sep 8, 2022 · 1 comment · Fixed by #27830
Labels
area/housekeeping Issue type for generalized tasks not related to bugs or enhancements
Milestone

Comments

@marcwrobel
Copy link
Contributor

Description

GitHub action versions seems rarely updated. For instance ci-actions-incremental.yml is still using action/checkout@v2 even if action/checkout@v3 has been released a few months ago.

Dependabot is used in the project for managing some of the Maven and Gradle dependencies. But it can also manage GitHub actions version (package ecosystem github-actions).

Should Dependabot be used for managing GitHub actions versions ?

Implementation ideas

Add the following to https://github.com/quarkusio/quarkus/blob/main/.github/dependabot.yml :

  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: daily
      time: "21:00"
      timezone: Europe/Paris
    open-pull-requests-limit: 4
    labels:
      - area/devtools
    rebase-strategy: disabled
@marcwrobel marcwrobel added the area/housekeeping Issue type for generalized tasks not related to bugs or enhancements label Sep 8, 2022
@geoand
Copy link
Contributor

geoand commented Sep 9, 2022

Interesting idea. Would you like to open a PR for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/housekeeping Issue type for generalized tasks not related to bugs or enhancements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants