Repository navigation
chore(deps): consolidate October toolchain updates - #110
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
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.
Summary
Consolidate the current Dependabot updates without changing product runtime sources or contracts. #106 and #107 split Vitest runners and coverage again despite the existing group; merge them together at 5.0.3 rather than landing either mismatch. Include the independent Ruff 0.16.10 and mypy 2.4.0 lock updates.
Explicitly name the coverage provider in the Vitest group and add a Node CI assertion rejecting unequal runner/provider manifest pins. Record the observed grouping recurrence in docs/06-field-notes.md. No registry URLs committed; preserve 473 unchanged npm integrity hashes.
Validation
Guardrails
No runtime workspace upload/sync or new egress path; package boundaries, protocol ownership, localhost/auth/provenance/redaction behavior unchanged. No actuator abstractions or release/publication. Repository-source push/merge only, authorized by the maintainer.
Closes #106
Closes #107
Closes #108
Closes #109