Sam & Claude
fdbd6b152f
The image shipped a hard pin (@earendil-works/pi-coding-agent@0.78.0) while 'pi upgrade' on hosts had moved to 0.80.2, so builds lagged. Switch Pi to the @latest dist-tag so every image bundles the newest Pi. To keep the floating spec traceable, record the version that actually got fetched in build-manifest.json as pi_version, derived from the bundled tarball name (earendil-works-pi-coding-agent-<version>.tgz) after fetch+install. fetch-npm-globals.sh now also echoes the resolved tarball so the build log shows the version a dist-tag resolved to. Other globals (bw) stay pinned. Image is node24, compatible with current Pi (the legacy-node20 dist-tag is for node20 only). Verified: fetch resolves @latest → 0.80.2; version extraction matches npm. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
823 B
Text
16 lines
823 B
Text
# Bundled npm global CLIs for offline firstboot/live operator use.
|
|
# Pin exact versions to prevent build-to-build drift — EXCEPT where a line uses
|
|
# a dist-tag (e.g. @latest) on purpose.
|
|
#
|
|
# Pi tracks `@latest` deliberately: each image ships the newest Pi. The version
|
|
# that actually got resolved at fetch time is recorded in build-manifest.json
|
|
# (`pi_version`), so the artifact stays traceable even though the spec floats.
|
|
# Pin a concrete version here instead if a build must be reproducible
|
|
# byte-for-byte.
|
|
|
|
@earendil-works/pi-coding-agent@latest
|
|
|
|
# Bitwarden CLI (`bw`) — headless access to the Clawdie Vaultwarden instance,
|
|
# used by clawdie-vault-fetch. Bundled offline so a booted image can pull agent
|
|
# secrets without a network npm install. See clawdie-ai/docs/VAULTWARDEN-SETUP.md.
|
|
@bitwarden/cli@2026.5.0
|