at.happyproto.registry.withdrawRelease
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"main": {
"description": "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 wherever that instance's proxy routing points. The release stays indexed and served by exact version, marked withdrawn, and the version can never be published again.",
"errors": [
{
"description": "The caller's identity could not be determined, so there is no repo to delete from.",
"name": "AuthRequired"
},
{
"description": "The slug or version could not name a release.",
"name": "InvalidRequest"
},
{
"description": "That version is not published from the caller's account, or was already withdrawn.",
"name": "ReleaseNotFound"
},
{
"description": "The record could not be deleted from the caller's repo.",
"name": "Upstream"
},
{
"description": "The registry has no identity configured.",
"name": "NotConfigured"
}
],
"input": {
"encoding": "application/json",
"schema": {
"properties": {
"slug": {
"description": "The package slug.",
"maxLength": 128,
"type": "string"
},
"version": {
"description": "The version to withdraw, as published.",
"maxLength": 256,
"type": "string"
}
},
"required": [
"slug",
"version"
],
"type": "object"
}
},
"output": {
"encoding": "application/json",
"schema": {
"properties": {
"uri": {
"description": "The release record deleted.",
"format": "at-uri",
"type": "string"
}
},
"required": [
"uri"
],
"type": "object"
}
},
"type": "procedure"
}
},
"id": "at.happyproto.registry.withdrawRelease",
"lexicon": 1
}
Metadata
- DID
-
did:plc:mo7vq4jbioxwafy5zkcc3eux - CID
-
bafyreich2ugcnjjpom2vs6ywnbvgb4irkgxlrq5prek2m3gtz3iav2zjma - Indexed At
- 2026-10-19 18:20 UTC
- AT-URI
-
at://did:plc:mo7vq4jbioxwafy5zkcc3eux/com.atproto.lexicon.schema/at.happyproto.registry.withdrawRelease
Similar Lexicons
Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
One release by exact version. Served whatever its status, including `deleted`: that is the left-pad protection the registry exists for.
-
com.atproto.repo.deleteRecord procedure
Delete a repository record, or ensure it doesn't exist. Requires auth, implemented by PDS.
-
at.happyproto.registry.publishRelease procedure
Publish a version of a plugin to the caller's repo. Writes a software.release.manifest carrying the artifact, the changelog as a site.standard.document when one is given, the software.release.version, and the channel na…
-
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.
-
at.happyproto.registry.retryRelease procedure
Copy a pending release's artifact again. A release is listed only once the registry has copied its artifact, which it tries once when it first indexes the release; this is how the release's publisher tries again after t…