at.happyproto.registry.publishRelease

happyproto.at

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "Check a release against the rules the indexer applies, and optionally write it to the caller's repo. The indexer validates a record only after it is published and skips an invalid one quietly, so a publisher writing the record itself gets no feedback; this answers the same refusal before the record exists. Pass validateOnly to check a record without writing it. Like every XRPC procedure this needs an authenticated caller, so validateOnly is a dry run rather than an anonymous one.",
      "errors": [
        {
          "description": "The caller's identity could not be determined, so there is no publisher to check the profile against and no repo to write to.",
          "name": "AuthRequired"
        },
        {
          "description": "The record is not a release the indexer would accept. The message names the reason.",
          "name": "InvalidRecord"
        },
        {
          "description": "That version is already published, or was withdrawn. A version is immutable once released and never reusable; publish a new one.",
          "name": "VersionExists"
        },
        {
          "description": "No profile is indexed at that slug, so the release would index against nothing.",
          "name": "ProfileMissing"
        },
        {
          "description": "The record could not be written to the caller's repo.",
          "name": "Upstream"
        },
        {
          "description": "The registry has no identity configured.",
          "name": "NotConfigured"
        }
      ],
      "input": {
        "encoding": "application/json",
        "schema": {
          "properties": {
            "record": {
              "description": "An at.happyproto.plugin.release record. Its package and version decide the record key, as the record lexicon requires of them.",
              "type": "unknown"
            },
            "validateOnly": {
              "default": false,
              "description": "Check the record and write nothing. Still requires authentication, as every procedure does.",
              "type": "boolean"
            }
          },
          "required": [
            "record"
          ],
          "type": "object"
        }
      },
      "output": {
        "encoding": "application/json",
        "schema": {
          "properties": {
            "cid": {
              "format": "cid",
              "type": "string"
            },
            "uri": {
              "description": "The record written. Absent when validateOnly was set.",
              "format": "at-uri",
              "type": "string"
            },
            "valid": {
              "description": "Always true; an invalid record is an error, not a result.",
              "type": "boolean"
            }
          },
          "required": [
            "valid"
          ],
          "type": "object"
        }
      },
      "type": "procedure"
    }
  },
  "id": "at.happyproto.registry.publishRelease",
  "lexicon": 1
}

Validate Record

Validate a record against at.happyproto.registry.publishRelease

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:mo7vq4jbioxwafy5zkcc3eux
CID
bafyreih5q5yjgn7cnnt5bufici6cka2iadgepr7pxrzdu5y7weoistyxly
Indexed At
2026-10-19 18:20 UTC
AT-URI
at://did:plc:mo7vq4jbioxwafy5zkcc3eux/com.atproto.lexicon.schema/at.happyproto.registry.publishRelease

Version History (2 versions)

Similar Lexicons

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

  • Publish an existing version's artifact under a new version, such as `1.2.0-rc.1` as `1.2.0`, without uploading it again. The new software.release.version points at the existing manifest. Optionally moves a channel to it…

  • Create or update a plugin project in the caller's repo. The first call writes the site.standard.publication, the at.happyproto.registry.project and the software.release.project, in that order, so each is indexed after w…

  • One version of a package. The record key is '<slug>:<version>'. A release at a given version is never modified: a registry that later sees a different CID at this key keeps the first and flags the conflict.

  • Delete a release record the caller published. This is how a publisher withdraws a release: it deletes from the caller's own repo as them, where com.atproto.repo.deleteRecord sent through a HappyView instance goes wherev…

  • Check a package profile against the rules the indexer applies, and optionally write it to the caller's repo. The indexer validates a record only after it is published and skips an invalid one quietly, so a publisher wri…

Lexicon Garden

@