Skip to content

Publish final completion release after external certifications #161

Description

@dayflaree

Goal

Publish the final completion release after all certification and production-signing issues are closed.

This is the final release gate after the project has real external evidence for the previously unvalidated claims.

Dependencies

Tasks

  • Decide release version and tag.
  • Update README, CHANGELOG, release docs, compatibility matrix, signing docs, runtime docs, compiler docs, Hammer docs, and model docs.
  • Remove or rewrite any stale limitation wording that is now validated.
  • Keep unvalidated future claims blocked by scripts/check-validation-claims.py.
  • Run full local gate.
  • Publish tag release.
  • Verify production signatures, checksums, SBOM, provenance, attestations, update manifest, and release assets.
  • Post final release evidence comment.
  • Close Completion epic: final certification and production release checklist #155 after this release issue is closed.

Acceptance criteria

  • Final release is published with signed artifacts.
  • Release notes link every completed certification issue.
  • SHA256SUMS, SBOM, provenance/attestations, and signatures verify.
  • The compatibility matrix contains only evidence-backed claims.
  • No proprietary tools, private credentials, game content, private assets, or private paths are committed or redistributed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:packagingRelease artifacts, installers, OS packagingarea:releaseVersioning, changelog, GitHub releasespriority:p1High priority after the MVP foundationstatus:blockedBlocked by external environment, credential, legal-tool, or release dependencytype:qualityReliability, correctness, validation, maintainability

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions