Release GERM 0.4.1 - #10
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.
What changed
outputValue, preserve source evidence, and explicitly withhold malformed or out-of-range controls.sound_id, Sonic Lineage, and Earworm identity stable across safe file renames.Why
The 0.4.0 integration expected a Cosmoaudition control field that is not present in the published modulation contract and allowed mutable filenames to leak into durable lineage identity. File companion operations also needed stricter provenance and transactional guarantees.
Validation
uv sync --extra dev --lockeduv run pytest -q- 218 passeduv run ruff check server testsnode --checkbash -nswift buildpip-audit: no known vulnerabilities, two documented ignoresuv lock --check,uv pip check, gitleaks,git diff --check, and public-file/path hygiene