Update ghcr.io/codize-dev/piston Docker digest to daf8db4

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/codize-dev/piston	digest	c8a33a5 → daf8db4

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Renovate PR Review Results

⚖️ Safety Assessment: ✅ Safe

🔍 Release Content Analysis

This Renovate PR updates the Piston Docker image digest from c8a33a5 to daf8db4, which represents 22 commits of changes from commit 19a184f to 775c9ae. The update includes:

Security Fixes (Critical):

• Isolate /dev/mqueue per sandbox (api/src/job.js:167) - Prevents cross-execution data leakage through POSIX message queues
• Isolate /dev/shm per sandbox (api/src/job.js:166) - Prevents cross-execution data leakage through shared memory

Security Testing Improvements:

• Added /dev/mqueue persistence test to verify sandbox isolation
• Added test-runner agent for automated sandbox exploit verification
• Enhanced exploit test documentation with descriptions and expected behaviors
• Fixed file persistence tests by removing non-existent sandbox directories

Package Updates:

• Added Rust 1.93.1 package
• TypeScript 5.9.3 improvements (enabled Node typings, fixed compile scripts)
• Go 1.25.5 package improvements (added go.mod, fixed compile scripts)

Infrastructure Updates:

• Updated base images: debian:bookworm-slim, buildpack-deps:bookworm
• Updated documentation (AGENTS.md) with test command updates
• Removed backward compatibility for TypeScript compile result copying

Key Change:
The primary security enhancement adds the --dir=/dev/mqueue:tmp flag to the isolate command in api/src/job.js:167, ensuring each sandbox execution has its own isolated message queue directory, preventing data leakage between executions.

🎯 Impact Scope Investigation

Direct Impact:

• File Modified: docker-compose.yaml (1 line changed)
• Image Update: Updates the API container image digest only
• No Breaking Changes: The change is a one-line addition to the isolate sandbox configuration

Codebase Analysis:

• Usage Locations: The ghcr.io/codize-dev/piston image is used in:
  • docker-compose.yaml:5 - Main API service (updated by this PR)
  • builder/Dockerfile:1 - Uses pinned commit 3809a44 (not affected)
  • .github/workflows/package-pr.yaml:97 - Pulls latest (will get update after merge)
  • .github/workflows/api-push.yaml:40-41 - Builds and pushes new images (not affected)

Configuration Impact:

• No new environment variables required - Uses existing isolate --dir flag syntax
• No API changes - Backward compatible security enhancement
• No schema changes - All existing API endpoints remain unchanged

Dependency Analysis:

• Runtime Dependencies: No changes to package.json or node dependencies
• Package Ecosystem: Changes only affect internal sandbox isolation, not language package interfaces
• Test Compatibility: All existing tests remain compatible; new security tests added

Production Deployment Impact:

• Simple container image pull and restart
• No database migrations required
• No configuration file updates needed
• No manual intervention required post-deployment

💡 Recommended Actions

Immediate Actions:

1. ✅ Merge this PR - This is a critical security fix with no breaking changes
2. ✅ Deploy immediately - The changes address cross-execution data leakage vulnerabilities
3. ✅ Restart the container - Run ./piston restart to apply the new image

Verification Steps (Post-Merge):

1. Verify sandbox isolation by running the mqueue persistence test twice:

   codize run --json tests/mqueue_persistance.py
   codize run --json tests/mqueue_persistance.py
   # Expected: No output on second run (file should not persist)

2. Verify shared memory isolation:

   codize run --json tests/file_persistance.py
   codize run --json tests/file_persistance.py
   # Expected: No output on second run

3. Run all security tests to confirm sandbox hardening:

   codize run --json tests/fork.py           # Fork bomb resistance
   codize run --json tests/fallocate.py      # Disk exhaustion resistance
   codize run --json tests/network.py        # Network isolation
   codize run --json tests/runaway_output.py # Output limit enforcement

No Manual Migration Required:

• Configuration files do not need updates
• API clients require no changes
• Existing workflows continue to function identically

🔗 Reference Links

• Commit Range: 19a184f...775c9ae (22 commits)
• Primary Security Fix: Isolate /dev/mqueue per sandbox
• Related Security Fix: Isolate /dev/shm per sandbox
• Security Test: Add /dev/mqueue persistence test
• Docker Image: ghcr.io/codize-dev/piston@sha256:daf8db4
• Changed File: api/src/job.js:167 (+1 line: --dir=/dev/mqueue:tmp)

Generated by koki-develop/claude-renovate-review