at.happyproto.registry.listReleases
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.
Details · query
| Kind | query |
|---|---|
| Authority | registry.happyproto.at |
| Indexed |
Query
query · GETParameters
query stringOutput
application/jsoncursor
stringErrors
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 matchLexicons 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.
-
A plugin's versions, most recently indexed first, whatever their lifecycle state.
-
List releases for a package, scoped to (did, package) and ordered by descending semver version. EXPERIMENTAL.
-
The releases a repository publishes.
-
Find packages. Deleted packages are never returned. With `q` the result is ranked by match and capped rather than paged, because the index's substring search takes no cursor; without it the result is paged.