io.agent.release
A record representing a software release.
Details · record, key string
| Kind | record |
|---|---|
| Record key | string |
| Authority | agent.io |
| Indexed |
Record
record · key stringProperties
Date and time the release was published.
dependencies
arrayThe software dependencies of this release.
details
string · uriA link to a human-readable page with more details about the release.
The name or identifier of the software.
maxLength: 100
notes
string · markdownRelease notes.
maxLength: 3000
The semantic version string, e.g., 1.2.0-beta.1
maxLength: 50
#asset
objectA link to a downloadable asset associated with a release.
#dependency
objectA software dependency of the release
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
at.happyproto.plugin.release
recordOne 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.
-
codes.tcm.release
recordA release of a tcm package, announced on the AT Protocol by its author.
-
dev.knotless.release
recordOne version of a package a repository publishes: its files, and the commit they were built from.
-
software.release.manifest
recordAn immutable collection of release artifacts. Written once and never updated: all facts (artifact digests, sizes, locations) are fixed at creation. Lifecycle changes use software.release.status records and software.release.channel moves. Any update to an existing release record is treated by indexers as a probable-compromise signal. Valid only when this record's DID matches the referenced project's DID.
-
software.release.version
recordAn immutable named pointer to a manifest. The record key is '{projectName}:{version}', making uniqueness per (project, version) mechanical and enabling AppView-free resolution. Version strings follow the project-name grammar (lowercase alphanumerics, interior hyphens) but allow dots. The version string cannot contain colons, but the rkey must contain exactly one colon. Valid only when same-DID with the referenced project, and only when target references a manifest of that same project.