Get the lifecycle events of a TEA Component Release

Lifecycle events for the object this endpoint is called on, as a TEA projection of the Common Lifecycle Enumeration (ECMA-428, 1st edition).

This is not a CLE document. The document envelope ($schema, identifier, updatedAt, and index / next page chaining) is not carried: the TEA object the response belongs to supplies the identity, and TEA has its own pagination. The event vocabulary, ordering and semantics are those of ECMA-428; the field shapes are TEA's. A consumer that needs a CLE document applies the mapping rules below and adds the envelope; a producer that holds a CLE document applies them in reverse. Publishers that need a bit-identical CLE 1.0.0 document publish it as a TEA Artifact in a release collection, as artifact type OTHER until a dedicated type exists; the same artifact may be referenced from more than one collection. The CLE endpoints are not a substitute for that document.

Mapping to ECMA-428:

• identifiers[] on componentRenamed uses the TEA identifier shape (idType, idValue); CLE uses type / value with the same meaning.
• A version specifier { version } names one version without a vers scheme, because a TEA server does not always know the package ecosystem. It corresponds to the CLE range vers:<scheme>/<version> once the scheme is known. { range } is a CLE range as-is.
• cle-event is one flat object. The fields ECMA-428 requires or permits for each event type apply as written there; servers shall populate the required ones and omit fields that do not belong to the type.

Selection. Servers shall return in events a subset of the events of the CLE data they hold for the component or product, and shall not alter an event beyond the mapping above. On a release endpoint, servers may omit events scoped to other versions: events whose versions do not cover the release's version, and released events whose version differs from it. Events that name no version, other than withdrawn events, apply to the component as a whole and are retained. Inclusion of withdrawn events follows the rule below. Servers shall not otherwise reduce the set, and in particular shall not collapse it to the latest event per type. Servers shall not renumber event id values. Servers shall include a withdrawn event if, and only if, they include the event it withdraws. definitions.support shall contain at least the policies referenced by the included events.

events shall be ordered by id descending, as in ECMA-428. A server that provides CLE for an object answers 200, with an empty events array when no event has been recorded yet. A server that does not provide CLE for the object answers 404 with error: NOT_IMPLEMENTED; error: OBJECT_UNKNOWN means the object itself is unknown.