Keep GitHub Actions up to date with GitHub's Dependabot#1583
Conversation
|
How can we run the new workflow to verify it works? Do we have to merge, then wait for the next calendar week to start? |
|
Merge it, and (if needed) a new pull request will normally be created within about 15 minutes. Example: |
|
This reduces maintenance burden of MAVProxy. I would like to try it. Approved! |
|
We could... but the PRs are likely to be ignored like the pnes for pymavlink are: https://github.com/ArduPilot/pymavlink/pulls?page=2&q=is%3Apr+is%3Aopen |
|
Better than waiting till the github actions are totally dead and CI breaks though? |
GitHub Actions are only used at CI test-time, while most other dependencies are also used at runtime. GitHub Actions have very infrequent major version changes . When GitHub Actions are upgraded, it often happens in batches. The There is a tradeoff between supply chain security and chattiness. Given that we have a few GHAs that are updated rarely and usually in batches, and we are using |
|
The author ping'd me about this so I've added it to the EUDevCall. I'm not really qualified to review the PR |
* [Keeping your actions up to date with Dependabot](https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot) * [Configuration options for the dependabot.yml file - package-ecosystem](https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)
|
Are there any remaining questions or todos on this one? |
Related to: