release: trace-spec 0.10.0 - #298
Merged
Merged
Conversation
Ships GHSA-vc4p-h84j-7qxj alongside the accumulated Unreleased work. Minor rather than patch: a record whose cnf.jwk carries private key material now fails schema validation. Such records were always invalid per the reference model, which has refused d/p/q/dp/dq/qi/k since it was written, but the verification path validates against the schema and the schema had no such constraint. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XbDBXDWWvMFa7c2jGgyq9t
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.
Version bump and changelog for 0.10.0, shipping GHSA-vc4p-h84j-7qxj alongside the accumulated
Unreleasedwork.Minor, not patch. A record whose
cnf.jwkcarries private key material now fails schema validation. Those records were always invalid permodels.TrustRecord, which has refusedd/p/q/dp/dq/qi/ksince it was written, but the verification path validates against the schema and the schema had no such constraint. A producer emitting one will now see it rejected.Tagging
v0.10.0after this merges triggers the PyPI publish workflow. The advisory gets published naming 0.10.0 as the patched version once it is on PyPI.Local test note, not a CI issue.
tests/test_docs_quickstart.py::test_first_record_tutorialfails on my machine onmainas well as here. Its subprocess resolvesagentrust_traceto the PyPI 0.9.0 install in site-packages rather than the repo, so it validates the tutorial against the previous schema. CI installs the repo and is green onmain. Worth a look separately, since a tutorial test that can silently grade against a released package rather than the tree is not testing what it appears to.🤖 Generated with Claude Code
https://claude.ai/code/session_01XbDBXDWWvMFa7c2jGgyq9t