Skip to content

This release adds 1 notable feature for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

ReleasePort's take

Light signal
editorial:auto 13d

SafeSandbox now warns users when the maxSnapshots limit is reached and recommends manual pruning instead of auto-pruning.

Why it matters: When maxSnapshots is hit, SafeSandbox will warn rather than prune automatically. Plan to monitor snapshots and prune manually before hitting the limit.

Summary

AI summary

Warns users when the maxSnapshots limit is reached and recommends manual pruning.

Changes in this release

Breaking Medium

SafeSandbox warns when maxSnapshots limit reached instead of auto-pruning.

SafeSandbox warns when maxSnapshots limit reached instead of auto-pruning.

Source: llm_adapter@2026-05-21

Confidence: low

Feature Low

Displays a user-visible warning when `maxSnapshots` limit is reached.

Displays a user-visible warning when `maxSnapshots` limit is reached.

Source: granite4.1:30b@2026-05-22-audit

Confidence: low

Feature Low

Suggests running `prune` manually to address Git slowdown or hang.

Suggests running `prune` manually to address Git slowdown or hang.

Source: granite4.1:30b@2026-05-22-audit

Confidence: low

Full changelog

Replace silent auto-prune with a user-visible warning when maxSnapshots limit is reached. Git can slow down or hang with too many snapshots — now SafeSandbox warns you and suggests running prune manually.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Automatic Git snapshots while AI agents edit your repo

Get notified when new releases ship.

Sign up free

About Automatic Git snapshots while AI agents edit your repo

All releases →

Related context

Beta — feedback welcome: [email protected]