Skip to content

OpenSecret: retire the legacy signed-PCR copy - #1659

Merged
AnthonyRonning merged 1 commit into
masterfrom
retire-legacy-pcr-mirror
Nov 19, 2026
Merged

AnthonyRonning merged 1 commit into
masterfrom
retire-legacy-pcr-mirror

Conversation

@AnthonyRonning

@AnthonyRonning AnthonyRonning commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Signed PCR approvals no longer get published to the legacy copy in OpenSecretCloud/opensecret. This is a documentation and procedure change; no code, workflow, PCR file or signing input changes.

Why

Approvals have been published in two places: this repository, and by hand in the root of OpenSecretCloud/opensecret for clients that predate the monorepo. The second copy existed only for clients that read the old URLs.

Both SDKs moved their history URLs to this repository on September 8, 2026 (79774ba5). That commit is in Research 3.4.0 and in SDK 4.0.0 for TypeScript and Rust, the same releases that moved those clients to Transport V2. Everything older speaks only Transport V1, which #1647 removed from the backend. So no client that can still reach a current backend reads the old copy, and nothing in the current source reads the old URLs.

Change

  • services/opensecret/docs/pcr-compatibility.md is now "Signed PCR files": one public location, a section recording that the legacy copy is retired and why, and validation and publication checks for this repository only. The manual legacy-publication section is gone.
  • It keeps one exception, with its command: a build from a commit that still serves Transport V1 can still be reached by old clients, so its approval would still go to the old copy.
  • The old repository itself is left as it is: not published to, pruned or archived.
  • The backend README, the SDK README, the SDK publishing and import docs, and the SDK skill say the same.

Not changed

  • scripts/pcr_compatibility.py and its tests. Its prepare command still serves the exception, and the file is a signing input.
  • The comment in .github/workflows/opensecret-eif-release.yml that says legacy mirror publication stays manual. I left the signing workflow untouched.
  • The Research proof page still links to the old repository as source code. That is a user-facing fix for its own change.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Signed PCR approvals were published twice: in this repository, which
Research 3.4.0 and both SDKs at 4.0 read, and by hand in
OpenSecretCloud/opensecret, which older clients read. Those older
clients speak only Transport V1, which the backend no longer serves, so
nothing that can reach a current backend reads the old copy.

The procedure now publishes approvals here only and leaves the old
repository as it is. It keeps one exception, with its command: a build
from a commit that still serves Transport V1.

Co-Authored-By: Claude <noreply@anthropic.com>
@AnthonyRonning
AnthonyRonning merged commit fa92042 into master Nov 19, 2026
21 checks passed
@AnthonyRonning
AnthonyRonning deleted the retire-legacy-pcr-mirror branch November 19, 2026 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant