release: 0.1.0-alpha.4 - #54
Merged
Merged
Conversation
Carries one fix: release.yml passed the built tarball to `npm publish` as `npm-dist/*.tgz`, which npm parses as a GitHub shorthand rather than a path, so the npm half of a release could never publish (#53). No SDK behaviour changes. The Python and TypeScript packages are identical to 0.1.0-alpha.3 apart from the version string. That string is inside the hashed envelope, so it moves every evidence digest: compatibility/golden/evidence-chain.json is regenerated from EvidenceAccumulator, and the cross-language tool_transcript assertion moves to a1361148f34e3ce16db7a2620572ada7c0cbe830eb7da1027f5837e00e3d5929 in both SDKs. Python 114 passed with 41 subtests, TypeScript 41 pass 0 fail. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015QRxFm1Z1kE9iraPspwr7j
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.
Cuts
0.1.0-alpha.4, following the file set of the last release commitdb3b785exactly: the same 39 files, none added and none missed.What is actually in this release
One fix, #53:
release.ymlpassed the built tarball tonpm publishasnpm-dist/*.tgz, and npm parses anya/bargument as a GitHub shorthand rather than a path, so the npm half of a release could never publish.No SDK behaviour changes. The Python and TypeScript packages are identical to
0.1.0-alpha.3apart from the version string.Why 35 files are a substitution and four are not
The version string is inside the hashed envelope, so bumping it moves every evidence digest. 35 files are pure substitution,
+40/-40, with zero lines touching anything but the version. The other four are regenerated from the code rather than edited:compatibility/golden/evidence-chain.jsonEvidenceAccumulator; digests now19b8a3bb...and7146bc82...tests/test_trace_adapter.pytool_transcript.hashmoves toa1361148...packages/typescript/test/trace-finalizer.test.tsCHANGELOG.mdThat the two SDKs land on the identical digest is verified here rather than assumed: Python 114 passed with 41 subtests, including
test_repository_gateswhich enforces version consistency across the tree, and TypeScript 41 pass, 0 fail.Context
agentrust-telemetry 0.1.0a3published to PyPI today, which activated the pending trusted publisher that was days from expiring.publish-npmfailed on the defect #53 fixes, andrelease-assetsskipped because it needs both. A re-run of that release cannot help: the run is pinned todb3b785and a re-run replays the workflow file at that commit, which still has the bug. Hence a fresh tag.🤖 Generated with Claude Code
https://claude.ai/code/session_015QRxFm1Z1kE9iraPspwr7j