Repository navigation
trace-verify 0.3.1
Metadata-only release. No behaviour change to the verifier.
What this fixes
trace-verify 0.3.0 on PyPI serves [project.urls] pointing at agentrust-io/trace-registry, which is private. Anyone who installed the package and followed its Documentation or Homepage link got a 404.
The URLs were corrected on main in #38, after v0.3.0 was tagged and without a version bump, so PyPI has been serving the stale metadata ever since. There was nothing left to fix in the URLs themselves. The version bump is the fix.
Closes the remaining half of agentrust-io/trace-spec#138, via #43.
After this release
| Link | Before | After |
|---|---|---|
| Homepage | agentrust-io/trace-registry (private, 404) |
public trace-spec |
| Documentation | trace-registry/.../docs/anchor-format.md (404) |
anchor format in trace-spec |
| Changelog | trace-registry/.../CHANGELOG.md (404) |
public |
| Bug Tracker | trace-spec/issues |
unchanged |
Worth stating plainly, since this package exists to verify that evidence resolves: a published artifact pointing at a repository nobody can reach is the same failure the anchor format rules are written to prevent. It went unnoticed for eleven days.