Skip to content

Add CI validation against results_v4 schemas#1

Merged
rcannood merged 1 commit into
mainfrom
ci/validate-results
Jun 27, 2026
Merged

Add CI validation against results_v4 schemas#1
rcannood merged 1 commit into
mainfrom
ci/validate-results

Conversation

@rcannood

Copy link
Copy Markdown
Member

Adds CI that validates every results_v4 release against the canonical JSON Schemas.

What

  • Add common_resources as the common/ submodule (pinned to main), which carries the canonical schemas/results_v4/ JSON Schemas.
  • Add scripts/validate_results.py: builds a schema registry from common/schemas/results_v4 so inter-schema $refs resolve locally (no network), then validates each <task>/<version>/ release. metric_info.json is optional; the other five files are required.
  • Add .github/workflows/validate.yml to run it on push and PR.

Notes

  • Validated locally against all 16 current releases: all pass.
  • Companion to Update results_v4 schemas common_resources#39 (now merged), which made schemas/results_v4 canonical and switched the $id/$ref URLs to the GitHub raw location.

- Add common_resources as the common/ submodule (pinned to main), which
  carries the canonical schemas/results_v4 JSON Schemas.
- Add scripts/validate_results.py: builds a schema registry from
  common/schemas/results_v4 (refs resolve locally, no network) and validates
  each <task>/<version> release file against its sub-schema (metric_info optional).
- Add .github/workflows/validate.yml to run it on push/PR.
@rcannood
rcannood merged commit 0207ca3 into main Jun 27, 2026
1 check passed
@rcannood
rcannood deleted the ci/validate-results branch June 27, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant