clawdie/clawdie-iso
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
clawdie-iso/packages/npm-globals.txt

17 lines
823 B
Text
Raw Normal View History

Pin ISO npm global CLI versions Use packages/npm-globals.txt as the source of truth for offline npm CLI tarballs, update Pi to 0.75.5, and keep Claude Code out of the XFCE USB path. --- Build: not run — ISO build not requested Tests: pass — sh -n fetch-npm-globals and shell-npm-globals; pinned npm pack smoke passed
2026-05-24 20:12:27 +02:00
# Bundled npm global CLIs for offline firstboot/live operator use.
build: track Pi @latest, record resolved version in build-manifest 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>
2026-06-24 01:59:29 +02:00
# Pin exact versions to prevent build-to-build drift — EXCEPT where a line uses
# a dist-tag (e.g. @latest) on purpose.
Pin ISO npm global CLI versions Use packages/npm-globals.txt as the source of truth for offline npm CLI tarballs, update Pi to 0.75.5, and keep Claude Code out of the XFCE USB path. --- Build: not run — ISO build not requested Tests: pass — sh -n fetch-npm-globals and shell-npm-globals; pinned npm pack smoke passed
2026-05-24 20:12:27 +02:00
#
build: track Pi @latest, record resolved version in build-manifest 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>
2026-06-24 01:59:29 +02:00
# 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.
Pin ISO npm global CLI versions Use packages/npm-globals.txt as the source of truth for offline npm CLI tarballs, update Pi to 0.75.5, and keep Claude Code out of the XFCE USB path. --- Build: not run — ISO build not requested Tests: pass — sh -n fetch-npm-globals and shell-npm-globals; pinned npm pack smoke passed
2026-05-24 20:12:27 +02:00
build: track Pi @latest, record resolved version in build-manifest 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>
2026-06-24 01:59:29 +02:00
@earendil-works/pi-coding-agent@latest
Wire encrypted secrets: Vaultwarden fetch + per-agent seed import Two parallel, additive paths so a host gets its secrets out of the box; the manual setup wizard stays the floor (no config = no-op). clawdie-vault-fetch (new): language-neutral bw bridge. Reads a 0600 ~/.config/vault-bootstrap.env, pulls keys from the agent-secrets collection (item name = env var name, value in password field, so no jq), prints KEY=VALUE or --write-env upserts 0600. Exit codes distinguish skip (3, no bootstrap) / broken (1) / no bw (4). Pinned @bitwarden/cli@2026.5.0 for offline bundling; staged in configure_live_operator_session. clawdie-live-seed: extend the CLAWDIESEED FAT32 importer from the authorized_keys allowlist to a per-agent directory convention — /<agent>/ with env (merged 0600), harness.toml (pi|zot|local), soul/ (staged), ssh/authorized_keys. Live USB single-agent (first dir = active); extra dirs staged + flagged for deployed multi-agent. Optional consume-and-shred. Import core is unit-testable via CLAWDIE_SEED_TEST. README rewritten to document the per-agent contract and the operator decision to allow plaintext secrets on the seed (seeded sticks are secret-bearing media; 0600 landing + shred mitigations). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-16 08:46:01 +02:00
# 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
Reference in a new issue Copy permalink