Align module release documentation with implemented behavior
This commit is contained in:
@@ -44,7 +44,10 @@ shared files. An explicit list replaces those defaults. Each explicit file must
|
||||
exist in the candidate, even when no file checks are enabled. Paths are literal,
|
||||
repository-relative files with no glob semantics and may select a file outside
|
||||
the chosen module. ReleaseKit deduplicates them with module inputs by path. This
|
||||
field does not enable any checks.
|
||||
field does not enable any checks or expand Go test, vet, or package-compilation
|
||||
scope. Automatic file inputs stop at independent nested-module boundaries;
|
||||
vendored files remain included. Reference inspection can read destinations
|
||||
elsewhere in the captured repository without adding them to those inputs.
|
||||
`validation.go.race` enables the race detector for the single standard Go test
|
||||
suite. `validation.go.full_vet` runs a separate native `go vet` pass after that
|
||||
suite succeeds; ReleaseKit disables test-time vet for that suite to avoid
|
||||
@@ -57,7 +60,8 @@ executable, or create an artifact manifest. Omitted or empty `compile_targets`
|
||||
selects no package-compilation pass. When `full_vet` is omitted or false, the
|
||||
test command keeps its existing vet behavior. These settings are independent.
|
||||
`validation.go_format` checks regular committed Go blobs with the Go formatter
|
||||
used to build ReleaseKit. It includes vendor and nested-module source, ignores
|
||||
used to build ReleaseKit. It uses the selected file inputs, including vendor and
|
||||
explicit shared files, and ignores
|
||||
symlink blobs and the worktree, and reports every selected path whose bytes
|
||||
change under formatting. It never writes formatted bytes back. Omitted or false
|
||||
disables the check. It runs after tests, selected full vet, and selected package
|
||||
@@ -92,7 +96,8 @@ of `GOWORK`; it does not select or change the workspace used by Go commands,
|
||||
and vendored contents remain in scope. Omitted or false disables it. When
|
||||
`validation.module_distribution.local_replacements` is true, it parses the
|
||||
selected module's committed `go.mod` declarations. Vendored contents remain in
|
||||
scope, while independently released nested modules are excluded. It reports
|
||||
scope; an explicit shared-file selection can include an individual declaration
|
||||
from another module. It reports
|
||||
`replace` directives whose replacement has no version. These filesystem
|
||||
replacements include relative and absolute paths; versioned module replacements
|
||||
are permitted. Committed `go.mod` symlinks are resolved within the candidate,
|
||||
|
||||
Reference in New Issue
Block a user