Skip to content

Add schema_version to test configs - #205

Open
helia77 wants to merge 1 commit into
mainfrom
structure-and-version
Open

helia77 wants to merge 1 commit into
mainfrom
structure-and-version

Conversation

@helia77

@helia77 helia77 commented Aug 20, 2026 •

Copy link
Copy Markdown
Collaborator

Follow-up to bilayer-containers/bilayers-schema#11, which adds schema_version as a required top-level key to the schema (read G from issue bilayer-containers/bilayers-schema#8.

Changes in:

  • correct_validation_config.yaml needs it, the test asserts "No issues found".
  • The two configs under tests/fixtures/ get it for consistency. generate does not validate and no template reads the key, so the golden files are unchanged.

Important note - why CI fails here

bilayers repo installs bilayers-schema and bilayers-algorithms from the tip of their main branches (not any pinned release), so CI here breaks the moment the schema PR merges and stays broken until the algorithms PR merges.
SO → Merge the algorithms PR right after schema's. The red gap is just the minutes between the two merges.

Merge order: bilayers-schema → bilayers-algorithms → bilayers.

@helia77
helia77 requested a review from rajavishah August 20, 2026 21:42
@helia77 helia77 added the enhancement New feature or request label Aug 20, 2026
@rajavishah

Copy link
Copy Markdown
Collaborator

Approving this!
Note - to merge this PR into main post param-secret is all baked into main across 4 repos

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants