Repository navigation
Patch pytest in isolated integration development environments - #3
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.
Updates pytest from 9.0.2 to 9.0.3 in both optional integration environments and refreshes their locks. Published v1 and local-model study artifacts remain unchanged.
Adds a separate v2-security deterministic baseline for the new dependency identity. Two fresh 13-case Docker runs matched byte-for-byte; every outcome and SQLite snapshot also matches v1. Only the dependency-file source hashes differ. CI compares current execution against the new baseline with the same strict verifier.
Validation: 40 integration tests and 27 local-model tests pass (2 existing skips); local-model Ruff passes; all 17 core canonical artifacts reproduce. Full installed optional-integration environments audit clean. No inference ran. The archived local-model manifest still rejects the changed environment, and a future model run requires a separately reviewed manifest and identity.