config: enable validation framework for onboarded repositories#245
Merged
hdamker merged 1 commit intocamaraproject:mainfrom Apr 29, 2026
Merged
Conversation
This was referenced Apr 29, 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
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.
What type of PR is this?
repository management
What this PR does / why we need it:
Flips per-repo validation stage from
advisory(central default) toenabledfor production repositories running the v1-rc validation framework, and
pre-stages two repositories with onboarding PRs in flight.
Effective immediately for the 12 repositories with
camara-validation.ymlalready installed. The entries for DeviceIdentifier and EdgeApplicationManagement
are pre-staged and become effective once their respective onboarding PRs merge.
Per-repo follow-ups outside this PR: disable the v0 caller workflows
(
pr_validation_caller.yml,spectral-oas-caller.yml) via the Actions APIand file a tracking issue per repo for eventual file removal at v1 GA
(precedent: SimpleEdgeDiscovery#164).
Which issue(s) this PR fixes:
Tracked under camaraproject/ReleaseManagement#484.
Special notes for reviewers:
Schema is permissive (
additionalProperties: true); pre-staged entries forrepositories without
camara-validation.ymlare inert until each repo'sonboarding PR merges.
Inline date comments (
# YYYY-MM-DD) record when each entry was added so thefile's rollout timeline is readable without git-log spelunking.
Changelog input
Additional documentation