chore: merge main into validation-framework (pre-E2E sync)#251
Merged
hdamker merged 5 commits intocamaraproject:validation-frameworkfrom Apr 30, 2026
Merged
Conversation
…view-legacy chore: remove deprecated api-review legacy files
camaraproject#247) * config: pre-stage CustomerInsights at enabled * config: drop EdgeApplicationManagement pre-staged annotation
…t#242) * docs: rewrite README around v1-rc / v0 split * Add hint how to get onboarded
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.
What type of PR is this?
What this PR does / why we need it:
Forward-merge of
mainintovalidation-frameworkso the next announcement-readiness E2E runs on a VF tip that already includes the latestmaincontent. Pairs with the planned VF → main promotion next week.Brings 4 commits / 6 files across:
4cf9202— README pointer to validation framework documentatione61063b— validation-settings.yaml: CustomerInsights pre-stage, EdgeApplicationManagement finalized8de430+9dff2b7— remove deprecated api-review legacy files (4 files, ~4400 lines)Auto-merge resolved
config/validation-settings.yamlcleanly withortstrategy; no manual conflict resolution.Which issue(s) this PR fixes:
None — routine sync.
Special notes for reviewers:
mainvia PRs docs: add pointer to validation framework documentation #242/chore: remove deprecated api-review legacy files #243/config: pre-stage CustomerInsights, finalize EdgeApplicationManagement #247.# pre-stagedannotations on the DeviceIdentifier and CustomerInsights entries inconfig/validation-settings.yamlare now stale (both repos went live earlier today); not cleaned in this chore merge to keep the diff narrow — opportunistic follow-up later.@v1-rcstays ata95f42auntil the post-E2E advance.Changelog input
Additional documentation