Integrate / Pin a release

Keep a reproducible reference

A semantic release identifies a specific state of accepted semantic records. Preserve its identity when storing or comparing results.

Inspect the current data#

Open Releases for the public collection manifests. Reference-data versions and protocol-finalized semantic releases are different records; do not treat one as proof of the other.

Pin an analysis#

Where a semantic method accepts release, pass the identifier you intend to use. The service rejects missing, unaccepted, or withdrawn releases rather than silently substituting the latest one.

A comparison or Illuminate request pins one release internally so a publication during the request cannot mix version labels across its results.

Verify the right thing#

verifyReleaseArtifact(id) checks the older local manifest and artifact hashes. verifyRelease({ releaseId, artifact }) verifies chain-grounded release membership and replays its consensus members. Neither should be described as independent semantic validation just because the bytes match.

Handle withdrawal#

Stop serving affected data when a release is withdrawn. Your caches, exports, and downstream copies need their own retention and withdrawal policy. A historic on-chain commitment cannot erase copies of source text.

Next: Protocol verification.