Rediscover Go settings only when Go work needs them
This commit is contained in:
@@ -64,7 +64,9 @@ Candidate checking captures and validates one clean committed source revision
|
||||
in `internal/candidate`. Its validation bridge calls `internal/validation` for
|
||||
the selected module's default offline Go suite, then runs product-specific
|
||||
checks once. Validation and its post-validation build callback share one local
|
||||
Go settings owner; the candidate package owns those builds and local-state
|
||||
Go settings owner. Each Go acquisition checks inherited and persistent inputs;
|
||||
settings are rediscovered when subsequent Go work needs them. An unavailable
|
||||
persistent-settings snapshot disables reuse. The candidate package owns builds and local-state
|
||||
rechecks; publication owns endpoint guards, tag creation, push, and recovery
|
||||
around that same candidate validation path. `internal/validation.CandidateTree` reads
|
||||
committed blobs lazily and resolves local destinations from committed entries;
|
||||
|
||||
Reference in New Issue
Block a user