v2.8.58 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.57 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.55 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.49 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.48 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.48 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.47 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).

v2.8.22 — tebako-runtime node (official Node.js distributions)

Tebako node runtime pairs

Release line: this tag IS the tebako product line the pairs build against.

Every runtime pair (the wrapper exe + its .tfs env image) ships with its
own metadata, written once by the build leg that produced it (spec 13 §2a):
the <asset>.sha256 sidecar next to every asset is the trust anchor (the
tebako store's own sidecar shape, spec 00 §8), and the
<stem>.manifest.json shard next to every pair carries exactly its
release-index entry. On signing-enabled lines every served name also
carries its own detached .asc (spec 09 §5).

There is no monolithic manifest.json / SHA256SUMS.txt release asset:
each shard IS its own release-index entry (the resolver's primary form),
and both monoliths are derivable conveniences, computed consumer-side
from the shards + the asset listing. The machine-readable
resolution index is this repo's tpkg-registry.yaml (spec 04 §2).