Release Risk Playground
Release Risk Playground
Aggregate quality signals across playgrounds into a release confidence recommendation.
Purpose
Read the release-confidence dashboard below, hunt risky signals across the manifest, deploy plan, contracts, and version alignment, then decide ship or hold.
Quality signals
A healthy gate weights every signal — open critical bugs should force hold.
Release confidence
77.5%
Recommendation: Proceed with caution
Open critical bugs: 2
Release manifest · schema
A healthy release pairs every schema change with a forward migration.
schema change ✓ · migration ✗
Deploy plan · rollback
A healthy deploy keeps one-step rollback ready when confidence drops.
rollback: unavailable / not configured
API contract diff
A healthy API bumps version when a breaking change ships.
- removed field: legacyStatus
Feature rollout
A healthy release gates risky behavior behind a feature flag.
Hotfix lane
A healthy hotfix runs its own test suite before promotion.
promotion allowed with tests: 0
Version alignment
A healthy release keeps build, changelog, and git tag on the same version.
Built version
2.4.1
Changelog top
2.4.0
Git tag
v2.3.9
Ship / hold decision
A healthy release process blocks promotion when confidence is below threshold and enforces the hold call.
Your call: undecided
Promotion gate: open
Known Intentional Issues (7)
Show hints (7)
Release ships a schema change with no accompanying database migration
Diff prisma schema against the latest migration and assert no pending model change lacks a migration file
Deploy has no rollback path if the release confidence score is below threshold
Set inputs so the recommendation is 'Hold' and assert the promotion path is blocked / a rollback action exists
Unversioned breaking change to a public API contract
Run a consumer contract test against the prior schema and assert it still passes, or that the breaking change is behind a new version
New behavior ships without a feature flag guarding it
Assert the new code path reads a feature-flag value and defaults to off in production config
Hotfix path has no test coverage before being promoted
Assert a hotfix cannot be promoted unless its own test run is green and recorded in the confidence inputs
Changelog and git tag drift from the version actually being released
Assert the latest git tag, VERSION file, and changelog top entry all reference the same version string
Confidence score weights do not block on a critical-bug count above zero
Set open critical bugs > 0 with otherwise strong signals and assert the recommendation is not 'Green'