Skip to content

Record PubLedge 0.2.5 provider state - #12

Merged
snapsynapse merged 2 commits into
mainfrom
codex/publedge-025-provider-state
Sep 12, 2026
Merged

snapsynapse merged 2 commits into
mainfrom
codex/publedge-025-provider-state

Conversation

@snapsynapse

@snapsynapse snapsynapse commented Sep 12, 2026

Copy link
Copy Markdown
Owner

PubLedge 0.2.5 is now independently visible on npm, the Official MCP Registry, the signed Git tag, and the GitHub Release. This receipt-only update records those observations, binds the registry tarball to the tested and release artifact SHA-256, clears the completed source candidate, and regenerates hosted discovery to report the evidenced 0.2.5 package.

The existing 0.2.4 evidence remains immutable. The publication-state regression fixtures now derive their synthetic next version from the observed provider version so a successful release does not make the negative tests vacuous.

Validation:

  • OBLIGATION_FIRST_DIR=/Users/snap/Git/obligation-first npm run verify:ci
  • npm 0.2.5 integrity: sha512-lW4/dL65pt0d6KuQ1qmZsOILHsTfoWLTyebc9vPyDCZYGI5ZprOV3grlyvyWqL+h7f412aqdumZ7GcN0nLJ0GA==
  • registry tarball SHA-256: 7eaea341b2d399cad25ec7d6e0314741a650d84773814cd039ae95d1674c6851
  • Official MCP Registry: active, latest, version 0.2.5
  • annotated tag target: 0105c7b38f650f1640fe6f14132ce8da479bc7de

@snapsynapse
snapsynapse merged commit ffe63c5 into main Sep 12, 2026
2 checks passed
@snapsynapse
snapsynapse deleted the codex/publedge-025-provider-state branch September 12, 2026 20:57
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