Skip to content

v2.7.1

Choose a tag to compare

View all tags
@rappdw rappdw released this 02 Oct 15:25
v2.7.1
87bb408
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This patch release has two fixes and one new document. No images rebuild: the generated entrypoint.sh, user-setup.sh and Dockerfile templates are unchanged since 2.7.0. schema_version stays 4, and SANDY_SANDBOX_MIN_COMPAT stays 2.0.0.

Fixed

  • Persistent package installs survive relaunches again (#417). Since 2.2.0, pip --user, uv python install, npm install -g, go install and cargo install wrote to the container's tmpfs home and were lost when the session ended. The mounts were removed by accident when #355 dropped the handoff tree. Sandy now mounts pip/, uv/, npm-global/, go/ and cargo/ from the sandbox again, as the README describes. Packages installed under 2.2.0–2.7.0 were never persisted, so reinstall them once.
  • Seed-once host writers refuse a planted symlink (#418, from the #368 Linux isolation stress run). Some files are seeded into an agent home only on first creation: the opencode config and the codex auth.json seed. Those writers now remove a symlink at the target instead of writing through it to wherever it points on the host. This is the same discipline §169 applies to settings.json. The redundant first-run statsig/ copy is also removed; the staged copy from #400 already covers it.

Docs

  • docs/security/ISOLATION_STRESS_LINUX.md is the Linux isolation stress report (#368). It records the status of each finding: L1 is fixed here (#418); L2 (#419) and L3 (#420) are tracked.

Known issues

  • Codex starts a new session on every launch instead of resuming the last one (#427). The fix lands in 2.8.0, together with sandy --login codex (#428), and a change so that SANDY_CODEX_AUTH=oauth withholds OPENAI_API_KEY (#429).
  • The scheduled Linux Integration workflow is red in §23 (the handoff-directories acceptance harness) on GitHub runners, as it has been since before 2.6.0 (#426).
  • test/run-tests.sh §123 can leave feature-entry supervisor loops running after the suite ends (#431). This affects the test suite only, not sandy.

Testing

  • CI (Linux): the Tests and proxy workflows pass on the release commit.
  • On the maintainer's macOS host: run-tests.sh passes on the fixes in this release.
Assets 2
Loading