Repository navigation
update to cmem-plugin-template v9.10.0 - #6
Merged
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.
Routine template update, v9.9.0 → v9.10.0.
What arrives:
check:deptryandcheck:trivyignore.claude/, so a git worktree created there no longer failstask checkwith findings from its own copy of the treeARG002on an argument whose presence the framework fixes is a settled suppression in the shipped rules;plugin-implementationsays why renaming it to_inputsis wrongtrivy-py-eccmoves to^0.76.0.1, with the lock refreshed for that package onlyThe update touched exactly the expected five files plus the lock — no conflicts, nothing to resolve.
Locally
task check:lintersis green on all four stages: ruff, mypy, deptry and trivy (0 vulnerabilities).