Say why CI's Python tools are not in dependabot.yml - #11
Merged
Conversation
The file already explains why firmware and managed-component versions are left to manual review. tools/requirements-ci.txt arrived after that note was written and is not covered by it, so the omission reads as an oversight rather than a decision. It is a decision. Dependabot would treat the .in and .txt as a pip-compile pair and regenerate the lock in its own environment, but this lock only installs if it is resolved for the runners specifically: resolved anywhere else it drops typing-extensions, and --require-hashes then refuses the entire install rather than fetching the missing package. Security alerts do not come from this file and continue to cover those packages, which is the part that matters for being told about a vulnerability. Co-Authored-By: Claude Opus 5 (1M context) <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.
dependabot.ymlalready explains why firmware and managed-component versionsare left to manual review.
tools/requirements-ci.txtarrived after that notewas written and is not mentioned, so its absence from the
updateslist readsas an oversight rather than a decision.
It is a decision, and this records it.
Dependabot would treat
requirements-ci.inandrequirements-ci.txtas apip-compile pair and regenerate the lock in its own environment. This lock only
installs if it is resolved for the runners specifically —
--python-version 3.12 --python-platform linux. Resolved anywhere else it omitstyping-extensions, whichanyioneeds on Python 3.12, and--require-hashesthen refuses the entire install rather than fetching the missing package.
Security alerts do not come from this file and continue to cover those
packages, which is the part that matters for being told about a vulnerability.
Only comments change; the configuration is untouched and still declares the
single
github-actionsecosystem.🤖 Generated with Claude Code