@nestledjs/upgrades

nestled-update — apply Nestled template upgrades to a cloned project.

A project created from nestled-template uses this package to pull published upgrades from its channel and apply them, tracking what it has already received in .nestled/upgrade-log.yaml. Note authoring stays private (only the template maintainer produces upgrades); every clone only ever consumes.

Model

• Manifest — the published feed: an ordered list of releases plus a pointer per channel (canary, stable). A clone on channel C applies every release with baseline < release.id <= channels[C]. Canary points ahead of stable, so the maintainer's fleet validates a release before the world sees it.
• Baseline — each clone remembers the release it started from. Fresh clones read it from a committed .nestled/template-version stamp; nestled-update init records it, and each apply advances it.

See docs/DISTRIBUTION-SPEC.md in the nestled-upgrader repo for the full design.

CLI

nestled-update init      # establish this clone's baseline + channel
nestled-update check     # show pending upgrades (no changes)
nestled-update status    # show channel, baseline, applied history
nestled-update apply     # apply pending upgrades

How it reads the feed

The feed lives in the public nestled-template repo under .nestled-upgrades/ (manifest.yaml + patches/*.diff). nestled-update adds the template as an upstream remote, git fetches the feed ref, and reads the manifest + patches via git show — no working checkout of the template. For local development/ testing, --manifest <file> reads a manifest off disk instead.

Configure the feed once at init:

nestled-update init --remote <template-git-url> --ref develop --channel stable

Status

• Phase 1 — manifest schema, baseline stamp, channel-aware pending, and init / check / status.
• Phase 2 — real apply: git-fetch feed transport, branch per run, 3-way patch application, package-release version bumps, verification gating with clean rollback on failure, baseline advancement, and optional --pr.

Still to come (producer side, in the private repo): the publish / promote-release / baseline-fleet commands that write releases into the template feed and move channel pointers.