chore(release): 0.4.1 - #51
Merged
Merged
Conversation
Patch release carrying the `--version` fix from #50. 0.4.0 reports `0.2.0` from `trace-tests --version`, which matters because the v0.2 profile cutover shipped in 0.4.0: `--version` is the command someone runs to check whether their suite matches their producer, and on 0.4.0 it answers with the version that cannot verify v0.2 records. The fix is on main but not on PyPI, so every installer still hits it until this ships. No behaviour change to conformance checking. The v0.2 profile requirement, module set, and every finding are identical to 0.4.0. Verified after the bump: - `trace-tests --version` -> 0.4.1, `importlib.metadata` -> 0.4.1. The version now tracks pyproject.toml with no code change, which is the point of #50. - `python -m pytest tests -q` -> 118 passed, 5 xpassed (pre-existing hardware-TEE xfails in tests/test_level2.py). - `python -m build` -> agentrust_trace_tests-0.4.1 sdist and wheel. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Why
Patch release carrying the
--versionfix from #50.0.4.0 reports
0.2.0fromtrace-tests --version. That matters more than a wrong string normally would, because the v0.2 profile cutover shipped in 0.4.0:--versionis the command someone runs to check whether their suite matches their producer, and on 0.4.0 it answers with the version that cannot verify v0.2 records. The fix landed on main in #50 but is not on PyPI, so every installer still hits it until this ships.What changed
pyproject.toml: version 0.4.0 to 0.4.1.CHANGELOG.md: promoted the Unreleased entry to v0.4.1.No behaviour change to conformance checking. The v0.2 profile requirement, the module set, and every finding are identical to 0.4.0.
Test plan
trace-tests --version->0.4.1,importlib.metadata.version()->0.4.1. Worth noting these tracked thepyproject.tomlbump with no code change at all, which is exactly what fix: read __version__ from distribution metadata #50 was for.python -m pytest tests -q-> 118 passed, 5 xpassed (pre-existingxfail(strict=False)hardware-TEE cases intests/test_level2.py)python -m build->agentrust_trace_tests-0.4.1.tar.gzandagentrust_trace_tests-0.4.1-py3-none-any.whl, so the release workflow will publish the right versionAfter merge
Cut the tag to trigger publishing, since
release.ymlfires onrelease: publishedand publishes to PyPI via OIDC trusted publishing:🤖 Generated with Claude Code