Repository navigation
ci: keep the GitHub Actions versions current with Dependabot - #17
Merged
Merged
Conversation
The workflow pins actions/checkout@v4 and actions/setup-python@v5, and nothing tells us when those go stale. The failure mode is a deprecated action or runner image breaking CI on an unrelated PR, which is the worst moment to discover it. Monthly, grouped into a single PR so it is one review rather than a trickle. No Python ecosystem entry, and the config records why: there is no requirements.txt or pyproject.toml to track. pytest is a host-side developer tool and the nodes run MicroPython flashed to the board, not installed packages. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Adds a Dependabot config for the
github-actionsecosystem — monthly, grouped into one PR so it is a single review rather than a trickle.The workflow pins
actions/checkout@v4andactions/setup-python@v5, and nothing currently tells us when those go stale. The failure mode is a deprecated action or runner image breaking CI on an unrelated PR, which is the worst moment to find out.No Python ecosystem entry, and the config records why: there is no
requirements.txtorpyproject.tomlfor Dependabot to track.pytestis a host-side developer tool, and the nodes run MicroPython flashed to the board rather than installed packages. The comment says to add apipentry if a pinned dependency file ever lands.Config file only. No code, and no change to what CI does.