Skip to content

Record v6.5.11 publication and post-release drift check #145

Description

@flyingrobots

Outcome

Current repository documentation and the post-release retrospective accurately describe the published git-cas v6.5.11 artifact and its proof boundaries.

Scope

Update README, STATUS, BEARING and release notes; record immutable publication and public-consumer receipts; add the required cycle retrospective and drift check. Preserve historical candidate receipts and prior-release evidence. Keep packaged documentation links valid and include v6.5.11 in package-documentation checks.

Prerequisite

#131 / PR #132 merged and published: signed v6.5.11 targets 1bcd631; workflow37008258240 succeeded. A fresh Docker consumer installed the registry artifact and passed six recovery regressions, store/restore, CLI version and signature/attestation verification.

Acceptance

  • Current release markers agree with the verified tag, source, registry and workflow receipts.
  • Historical candidate evidence remains explicitly pinned and unpublished at its original coordinates.
  • Packaged public Markdown links do not point to unpackaged local planning files.
  • Documentation contracts and relevant unit checks pass in COPY-based Docker.
  • The retrospective separates synthetic transport proof from downstream attachment/GC acceptance.

Exclusions and safe merge state

No runtime change, artifact replacement, version bump, tag rewrite or new publication. The already-published v6.5.11 remains immutable. Git-warp #923 owns downstream adoption; its public attachment APIs are separate work.

Activity

  1. added this to the v6.5.11 milestone on Oct 2, 2026
  2. added
    type:releaseRelease evidence, gate, or packaging work
    area:docsDocumentation, examples, or public guidance
    status:activeWork is actively being implemented or validated
    on Oct 2, 2026
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:docsDocumentation, examples, or public guidancestatus:activeWork is actively being implemented or validatedtype:releaseRelease evidence, gate, or packaging work

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions