Skip to content

v5.27.1 — Default packs hold, never block

Choose a tag to compare

View all tags
@ucsandman ucsandman released this 21 Aug 04:22
· 16 commits to main since this release
v5.27.1
bb40f75

Changed

  • Nothing in the default packs refuses outright any more. The risk-100 line of the catastrophe-only pack (seeded into every new org) and of the claude-code-starter pack was action: block. At score 100 the runtime cannot tell "wipe the disk" from "ship the site" (an irreversible deploy stacks to exactly 100: deploy 75 + deployment-pattern 10 + irreversible 15), and it was refusing a Vercel deploy with no approval card. Both lines are now require_approval: the hold lands on /approvals with one-click approve/deny, and the human decides. Renamed "Hold Mass-Destructive Operations for Approval"; policy ids unchanged.
  • Already-seeded orgs are migrated in place. scripts/auto-migrate.mjs flips any seeded "Block Mass-Destructive Operations" row (any org) to the hold shape on every deploy; matches the old name only, so it is a no-op once flipped. The /connect receipt sentence follows the new shape.

Platform-only release; SDKs are not republished (npm/PyPI stay at 5.26.0).

Assets 2
Loading