Simplify release validation gates
This commit is contained in:
@@ -26,7 +26,7 @@ policy and link to it rather than introduce additional release requirements.
|
||||
ConfigKit adopts a source-only Go module release model. The source tag and
|
||||
version-matched release note are the declared deliverables. Standalone binaries,
|
||||
container images, and separate binary/package-registry publication are not
|
||||
required. This does not waive source compilation, module hygiene, testing, or
|
||||
required. This does not waive source compilation, dependency maintenance, testing, or
|
||||
local target-build validation. Post-publication consumer retrieval is optional,
|
||||
as described under Release Model.
|
||||
|
||||
@@ -148,11 +148,17 @@ gate; historical release notes are unchanged.
|
||||
|
||||
ConfigKit provides one local release checker. Run it once against the final
|
||||
committed candidate using one maintained patch of the minimum supported Go line
|
||||
on Linux. It checks module hygiene, formatting and whitespace, the full offline
|
||||
suite with the race detector, static analysis, and CGO-disabled Linux amd64/arm64
|
||||
builds. Examples, documentation links, consumer fixtures, and package boundaries
|
||||
are covered by that suite, not separate repeated runs. Native package compilation
|
||||
is covered by the test run. A second toolchain is optional and non-gating.
|
||||
on Linux. It runs one full offline race suite, one full vet pass, and CGO-disabled
|
||||
Linux amd64/arm64 builds. The race suite protects library behavior, ownership,
|
||||
and concurrent use; it includes examples, documentation links, consumer fixtures,
|
||||
and package boundaries without separate runs. Full vet checks more than the
|
||||
subset normally run by tests, so test-time vet is disabled. The two cross-builds
|
||||
cover supported configurations that native race compilation does not. A second
|
||||
toolchain is optional and non-gating.
|
||||
|
||||
All Go checks use readonly module mode and an offline dependency cache.
|
||||
Formatting and whitespace remain ordinary development checks. Review module
|
||||
tidiness when dependencies change, rather than auditing it on every release.
|
||||
|
||||
Commit the release note and associated changes before release validation. Record
|
||||
the exact validated commit; revalidate if the candidate changes. Do not require
|
||||
|
||||
Reference in New Issue
Block a user