Skip to content

Release Validation Record

Keep the completed record private if it contains account identifiers, workflow links, or operational details. Do not record customer names, contact details, credentials, or raw customer data.

Release identity

  • Version / candidate:
  • Exact Git tag or ref:
  • Resolved commit SHA:
  • Edition(s):
  • Reviewer and date:
  • Archive-validation workflow run URL or ID (for this exact ref):

Product terms and support

Decision Outcome / approved terms Evidence reference
Software license and version
Source attribution and redistribution terms, by edition
Support boundary (scope, response target, duration, exclusions, escalation owner)
Update policy (supported release line, update window, security fixes, major updates)

Release archives

Edition Archive filename ZIP SHA-256 Embedded manifest verification (pass/fail) Archive-validation evidence
BigQuery
Snowflake

Validation runs

Edition Python / dbt / adapter Command Status (passed / skipped / failed) Target type (never credentials) Models/tests result Cost/bytes reviewed? Evidence reference
BigQuery Isolated dataset
Snowflake CI schema/non-prod

For cost evidence, distinguish billed currency from diagnostic usage: record BigQuery billed amount/currency separately from query bytes, and Snowflake billed credits separately from any invoice currency amount. Do not estimate a dollar total using a generic credit price.

Add one row per validation command/run, including separate parse, warehouse build, and clean-install runs. Do not mark a parse as warehouse validation or a planned run as passed.

Release audit

  • [ ] Actionlint version/checksum and Gitleaks version/image digest recorded; scanner behavior smoke check passed on safe and synthetic fixtures.
  • [ ] All third-party Actions use reviewed full commit SHAs; Dependabot/update review recorded.
  • [ ] Workflow trust-boundary review complete, including the trusted main push workflow, secret scope, CI target naming guards, and the private-plan branch-protection limitation.
  • [ ] Dependency advisory review recorded, including accepted exceptions and review dates.
  • [ ] Clean-checkout release archive validation passed for each included edition and exact candidate ref; per-edition ZIP checksum and embedded manifest were verified.
  • [ ] Two independent clean installs completed; elapsed time and blockers recorded.
  • [ ] CI parse and any credentialed warehouse builds have actual run links and results.
  • [ ] Incremental examples were run and compared with full refresh, or excluded from release claims.
  • [ ] Archive content and checksum reviewed; secret scanner findings resolved.
  • [ ] Source attribution, redistribution terms, software license, support, and update policy approved and recorded above with evidence.
  • [ ] Changelog, known limitations, and rollback/recovery notes prepared.
  • [ ] Product owner decision: release / hold / revise.

Known issues and accepted risks

Issue or risk Impact Owner Resolution or mitigation Accepted by / date