Keep GitHub Actions up to date with GitHub's Dependabot#2435
Keep GitHub Actions up to date with GitHub's Dependabot#2435danielaskdd merged 1 commit intoHKUDS:mainfrom
Conversation
* [Keeping your software supply chain secure with Dependabot](https://docs.github.com/en/code-security/dependabot) * [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) To see all GitHub Actions dependencies, type: % `git grep 'uses: ' .github/workflows/`
|
Automatic dependency updates pose the following issues:
Given the lack of significant benefits, manual inspection and updating of dependencies are recommended. |
|
The "system" in this case is the GitHub Action runtime (not your local system), and Dependabot is created by and recommended by GitHub as stated in the commit message above. Upgrades to Actions can be security fixes, such as: Which is missing here:
|
|
Due to compatibility requirements, certain modules such as numpy must remain on lower versions. Dependabot periodically raises PRs to trigger updates — how should this be addressed? |
|
I got your point. The let AI solved my concern in PR #2447. |
dependabot.ymlfile - package-ecosystemTo see all GitHub Actions dependencies, type:
%
git grep 'uses: ' .github/workflows/Description
[Briefly describe the changes made in this pull request.]
Related Issues
[Reference any related issues or tasks addressed by this pull request.]
Changes Made
[List the specific changes made in this pull request.]
Checklist
Additional Notes
[Add any additional notes or context for the reviewer(s).]