Skip to content

Sentinel Shield v2.0.0-beta.1 — Engine-only Beta

Pre-release
Pre-release

Choose a tag to compare

@bogdaniel bogdaniel released this 02 Jul 16:49
· 490 commits to master since this release
becec20

⚠️ Engine-only beta — read before adopting

Sentinel Shield v2.0.0-beta.1 is an engine-only beta release.

This release validates the Sentinel Shield policy engine, release gates, transactional installation and recovery model, workflow security controls, deterministic profile fixtures, and GitHub-verified engine CI.

Laravel and Symfony profiles are engine-tested and fixture-tested, but they were not independently validated in real consumer repositories for this release.

This release does not claim framework-validated, release-candidate, or general-availability readiness. The stable, supported line remains v1.x (latest v1.9.2). Adopt this beta for the engine itself — not for a production Laravel or Symfony application.

Under the engine-only release scope the evidence proves the reusable engine via its own default-branch CI (GitHub-verified), not any framework in a real adopter repository. required_evidence.laravel and required_evidence.symfony remain false, consumer_runs is empty, and the release validator prints FRAMEWORK LIVE-VALIDATION NOT INCLUDED.

What this release validates

  • Profile-policy resolution and effective-profile composition
  • Required / recommended / optional / one-of gate semantics and fail-closed enforcement
  • Local pipeline orchestration and stale-report protection
  • Source-acquisition safety and path-safety guards
  • Transactional install / sync / migration with fail-closed recovery
  • Release-evidence validation (structural + GitHub-verified)
  • Engine GitHub Actions workflows, workflow pinning, and security linting
  • Deterministic fixture validation

Deferred (not in this release)

  • Real Laravel consumer CI
  • Real Symfony consumer CI
  • Independent production-project adoption proof
  • External maintainer usability proof

Promotion to framework-validated or full-platform scope in a later cycle would require the corresponding real-consumer live-validation evidence.

Release evidence

Verify locally: sh scripts/validate-release-evidence.sh --verify-github

Migration documentation

Engine-only scope details

  • Release scope: engine-only
  • Engine commit: becec20ed3890032d722a6118deee4a2314d39e9 (PR #11 merge)
  • Engine CI: GitHub-verified ci-self-test + ci-pipeline (and supporting workflows) green on master at the engine commit