ship-preflight

Topics in the source

• ship-preflight (Stage ⑤.a)
• Overview
• Process
• Boundary
• How to invoke

The machine-checkable "PR ready != release ready" gate. Runs the harnessed-native harnessed release-preflight command, which inspects (read-only) whether the repo is ready to tag a release: | check | passes when | | ----- | ----------- | | changelog | ## [Unreleased] has entries, or a section exists for the valid target version | | version | A static valid SemVer is discovered, or supplied with --release-version | | git-clean | the working tree has no uncommitted changes | | tag-absent | a v tag does NOT already exist | Version sources are package.json.version, pyproject.toml [project].version, pyproject.toml [tool.poetry].version, and Cargo.toml [package].version. harnessed release-preflight --release-version takes highest priority; an invalid explicit value fails without falling back to manifests. Matching discovered versions are accepted. Conflicting valid versions fail closed and require an explicit override. No target version is inferred from git tags. Missing, dynamic, workspace-inherited or malformed versions cannot supply a static target. If no valid target can be determined, version fails and tag-absent is warn/not-run, never a check against the literal tag v. Version-spec

This is an excerpt. Refer to the complete source and its current requirements.