at.happyproto.registry.getRelease

One release by exact version. Served whatever its status, including `deleted`: that is the left-pad protection the registry exists for.

Repository @happyproto.at did:plc:mo7vq4jbioxwafy5zkcc3eux namespace authority
Details · query
Kindquery
Authorityregistry.happyproto.at
Indexed

Query

query · GET

Parameters

query string

did

requiredstring · did

slug

requiredstring

version

requiredstring

Semver without build metadata, exactly as the record key carries it.

Output

application/json

Errors

ReleaseNotFound

No release is indexed at that version.

NotConfigured

The registry instance has no identity configured (HAPPYPROTO_DID), so it cannot read its own state. An operator problem, not a caller's.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • One version of a plugin, by exact version, whatever its lifecycle state or availability.

  • Every release of a package, newest-indexed first, including withdrawn ones flagged `deleted` — a client resolving an exact version needs to see that it exists.

  • One package by publisher and slug. A withdrawn package is still returned, flagged `deleted`, because its releases stay resolvable.

  • The bytes of a blob the registry has copied, served from its own copy and never redirected to the publisher, so a version stays installable after its publisher deletes it. Name the blob either by version and kind or by its CID. Only blobs that an indexed manifest or publication references are served. The output encoding is `*/*`, as com.atproto.sync.getBlob's is; the media type is the one the blob was published with.

  • A plugin's versions, most recently indexed first, whatever their lifecycle state.