Skip to main content

Review release readiness

Use this workflow before promoting a release to production.

1. Create or update the release​

tiden release create \
  --product-id <product-id> \
  --version "$RELEASE_VERSION" \
  --environment staging \
  --url "$BUILD_URL"

2. Confirm telemetry uses the same release​

Your runtime SDK should use the same release value:

Tiden.init({
  dsn: process.env.TIDEN_DSN,
  release: process.env.RELEASE_VERSION,
  environment: 'staging',
})

3. Review open issues​

Open the release detail or Issues page and filter by release/environment. Resolve or ignore issues only after triage.

4. Check traceability​

Open Traceability for main or the release context. Look for:

  • no_test requirements.
  • not_run requirements.
  • Failing test cases.
  • Components with weak coverage.

5. Run the quality gate​

tiden gate check --product-id <product-id> --release <release-id>

If blocked:

  1. Open the gate page.
  2. Expand the blocking component.
  3. Follow fix hints.
  4. Recompute after fixes land.

6. Document risk acceptance​

If the verdict is risk-accepted, include a clear reason and approver. Do not use risk acceptance for unknown failures or untriaged production issues.