Release Process and Versioning

Follow the identity from source to publication

A release should let a reader answer: which source was reviewed, which checks ran, what was published, and which limitations remained? For v7.3.0, inspect the records below. Prospective release and asset links become evidence only after publication is remotely verified.

flowchart LR
    S["Reviewed source revision"] --> C["Required checks on that revision"]
    C --> T["Annotated immutable tag"]
    T --> R["Release + verified bundles"]
    R --> W["Published handbook verification"]

Loading

What to inspect

Record	Purpose
v7.3.0 release	Published notes and downloadable artifacts
Publication receipt	Exact commit, tag identity, checks, asset hashes, and publication observations
Designated review	Judgment, actual reviewer/context relationship, and scope
Exact gate results	Required jobs and explicitly disclosed diagnostics
v7.3.0 release policy	Rules governing this publication
Pre-publication authorization	Owner authorization, firing condition, and reviewer designation recorded before the candidate existed
v7.2.0 release	The previous support point; its records remain unchanged

Released notes match their committed sources. Annotated tags remain fixed. Later documentation improvements belong to the current handbook and wiki history; they do not change the released code or rewrite old evidence.

Documentation can improve between releases

This handbook explains v7.3.0 behavior while allowing clearer examples and navigation after publication. Canonical method links stay pinned to that release. Links to other repository documents, such as the maintainer guide and the release policy, point to those documents as they stood at the source commit named in the footer; newer versions may exist on the main branch. The wiki is a separate Git repository, so publication and live verification are distinct from a source commit.

An updated handbook does not prove a user's installation upgraded. Installation, loaded context, and exercised behavior require their own observations. See Installation and Harness Compatibility and Testing and Evaluations.

Future releases follow the release policy, with their own source identity and evidence.