v0.27.5

node build and stack launch now reuse a cached artifact for unchanged sources, with --rebuild to force a fresh build.

Released on September 3, 2026

Built node artifacts now live at ~/.peppy/built_nodes/<name>_<tag>/<fingerprint>.tar.zst (or .sif) rather than ~/.peppy/built_nodes/<name>_<tag>.tar.zst; update any scripts that reference the old fixed path.
peppy node build reuses a stored artifact when the staged sources are byte-identical to an earlier build's, skipping build_cmd or apptainer build and logging Reusing cached build of ....
The cache is a content-keyed directory tree that survives daemon restarts and carries built nodes to any machine booted from the same disk with a matching peppy version, OS, and architecture.
peppy stack launch reuses cached builds for every deployment, on the coordinator and on every peer, so relaunching the same launcher skips rebuilding unchanged nodes.
Pass --rebuild to peppy node build or peppy stack launch to rebuild from the staged sources even when a matching artifact exists, replacing it; this is independent of --force.