feat(config): parse, validate, and resolve the components model under schema_version 1 - #507
Merged
Merged
Conversation
… schema_version 1 Activate the reserved components block as a live config surface. A manifest may declare named components with a per-component path and tag_prefix, inheriting shared top-level defaults and overriding them per field. Validate that per-component tag namespaces are distinct and reject per-component overrides of global-only fields. A manifest with no components block is unchanged: the single-component path stays byte-identical. Refs #280, #281. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
This was referenced Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
components:manifest block exists only as a reserved, inert shape. Multi-component (monorepo) support is folding into v1 as the nativeschema_version 1model, so the config layer must accept and resolve components.Fix
Activate
components:as a live config surface:pathandtag_prefix, valid whenschema_versionis omitted or1(the too-new guard for>= 2is unchanged).components:block is unchanged: the single-component path stays byte-identical (no component dimension exists).Scope is the config layer only. Per-component workflow generation and the scoped state serializer land in follow-on increments; the behavioral e2e scenario arrives with generation.
Verification
go build ./...,go test ./...(2543 pass),go test ./... -race(2543 pass), andgolangci-lint run ./...all clean. The three embedded schema copies are re-synced and byte-identical (TestSchema_OnDiskCopiesAreByteIdentical), and every e2e scenario config still validates against the schema (TestSchema_ValidatesE2EScenarioConfigs).Refs #280, #281.