chore(dependabot): track github-actions dependency updates#42
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
github-actionsecosystem entry todependabot.ymlso Dependabot scans workflow files weekly and proposes action version bumps (grouped version + security updates, matching the existing ecosystems).Why
The repo wasn't tracking GitHub Actions updates at all. CI currently surfaces a deprecation warning for
azure/setup-helm@v4.3.1running on Node 20 (forced to Node 24 from 2026-06-16).That specific warning is not fixable today —
v4.3.1is already the latest tag, and the Node runtime is declared inside the action itself, not something we pin. Once Azure ships a Node-24 release, this Dependabot config will automatically open the bump PR. It also keeps the rest of the actions (actions/checkout, etc.) up to date going forward.