safe-chains v0.215.0
Released 2026-07-25 · View on GitHub
- feat *(engine)* Add the local working-copy archetypes
- feat *(vcs)* Re-research git's local working-copy surface under the facets
- feat *(aws)* Restructure secretsmanager from glob to researched sub-subs
- feat *(gcloud)* Restructure secrets from a glob into researched sub-subs
- feat *(aws)* Restructure kms from a glob into researched sub-subs
- feat *(aws)* Research iam's read-verb glob flags
- feat *(aws)* Research the s3api, logs and cloudtrail read-verb glob flags
- feat *(aws)* Research the ec2, rds, lambda and ecs read-verb glob flags
- feat *(aws)* Research the ssm, dynamodb, cloudformation, sns and sqs glob flags
- feat *(engine)* Recognize loopback network locations
- feat *(registry)* Gate a flag on its value naming this machine
- feat *(engine)* A local endpoint re-classifies a sub as its local archetype
- feat *(aws)* Classify dynamodb's item surface for local development
- feat *(engine)* Report WHICH facet refused a command
- feat *(engine)* Detect confusable archetypes mechanically
- fix *(registry)* Enforce the flag allowlist on profiled subcommands
- fix *(registry)* Require a profiled sub to declare its flag surface
- fix *(registry)* Enforce a researched flag list on first_arg glob families
- fix *(aws)* Dynamodb scan is a data-export, not a bulk-object-read
- fix *(registry)* A flag past
--is a positional, not an endpoint - fix *(registry)* Decide the loopback destroy rule by operation, not by name
- fix *(engine)* Derive the fail-closed sentinel from declared per-axis hazards
- fix *(engine)* The sentinel's operation was one an everyday level admits
- other *(engine)* Compose the loopback effect instead of swapping archetypes
- other *(repo)* Record the glob-family flag migration and its remaining set
- other *(repo)* Record the loopback feature's remaining work
- other *(repo)* Correct the install-clause claim in the unverified-axes note
- other *(engine)* Property-test the facet enumeration and the loopback host check