software.release.channel

A mutable named pointer to a version. Resolve the manifest through the referenced version. The record key is '{projectName}:{channelName}', making uniqueness per (project, name) mechanical and enabling AppView-free resolution. Channel names follow the project-name grammar (lowercase alphanumerics, interior hyphens, no dots). The project name cannot contain colons, but the rkey must contain exactly one colon. Valid only when same-DID with the referenced project and version.

Details · record, key any
Kindrecord
Record keyany
Authorityrelease.software
Indexed

Record

record · key any

Properties

name

requiredstring

Channel name (e.g. latest, next). Follows the project-name grammar. MUST match the record rkey after the colon.

  • minLength: 1
  • maxLength: 64

project

requiredstring · at-uri

The software.release.project this pointer belongs to. MUST be same-DID.

version

requiredref

Strong reference to the software.release.version this channel currently points to. MUST belong to the same project.

Similar lexicons

semantic match

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

  • An 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.

  • A software project. The record key is the project name itself, making duplicate names per repo impossible and enabling AppView-free resolution. Name grammar (normative prose): 1 to 64 lowercase ASCII alphanumerics and interior hyphens only, no dots or colons, no leading or trailing hyphen.

  • An 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.

  • The version a plugin's channel points at.