chore: merge main into validation-framework#246
Merged
hdamker merged 19 commits intocamaraproject:validation-frameworkfrom Apr 29, 2026
Merged
chore: merge main into validation-framework#246hdamker merged 19 commits intocamaraproject:validation-frameworkfrom
hdamker merged 19 commits intocamaraproject:validation-frameworkfrom
Conversation
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 6 to 7. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v6...v7) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 47.0.2 to 47.0.5. - [Release notes](https://github.com/tj-actions/changed-files/releases) - [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md) - [Commits](tj-actions/changed-files@8cba46e...22103cc) --- updated-dependencies: - dependency-name: tj-actions/changed-files dependency-version: 47.0.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/github-script](https://github.com/actions/github-script) from 8 to 9. - [Release notes](https://github.com/actions/github-script/releases) - [Commits](actions/github-script@v8...v9) --- updated-dependencies: - dependency-name: actions/github-script dependency-version: '9' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…thub_actions/actions/github-script-9 chore(deps): bump actions/github-script from 8 to 9
…thub_actions/tj-actions/changed-files-47.0.5 chore(deps): bump tj-actions/changed-files from 47.0.2 to 47.0.5
…hub_actions/actions/upload-artifact-7 chore(deps): bump actions/upload-artifact from 6 to 7
Add a second dependabot.yml entry with target-branch: validation-framework so Dependabot creates dependency update PRs against validation-framework in addition to main, preventing the branch from falling behind during the RC period. Once validation-framework merges into main, the second entry should be removed as part of the merge cleanup.
…dation-framework-target chore: enable Dependabot on validation-framework branch
The functional Regression Runner workflow lives on the validation-framework branch (see camaraproject#172). This stub only exists so the workflow appears in the Actions UI dropdown — workflow_dispatch requires the workflow file to be present on the default branch to be registered as a dispatchable event type. The stub supports workflow_dispatch only (no push) and fails fast with a clear error message if actually dispatched against main, so accidental dispatches are visibly wrong instead of silently routed to the validation-framework version. When validation-framework merges into main at v1 GA, this stub will be replaced by the real file as part of that merge. Tracks ReleaseManagement#483.
…ner-stub Add Regression Runner workflow stub on main
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 47.0.5 to 47.0.6. - [Release notes](https://github.com/tj-actions/changed-files/releases) - [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md) - [Commits](tj-actions/changed-files@22103cc...9426d40) --- updated-dependencies: - dependency-name: tj-actions/changed-files dependency-version: 47.0.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…thub_actions/tj-actions/changed-files-47.0.6 chore(deps): bump tj-actions/changed-files from 47.0.5 to 47.0.6
…branch Add a third dependabot.yml entry covering the npm dependencies in validation/package.json (Redocly CLI, Spectral, gherkin-lint) so they receive weekly update PRs alongside the existing GitHub Actions tracking. Once validation-framework merges into main, both target-branch entries should be removed and replaced with main-targeted equivalents.
Adds the central validation settings file at its target location. No consumer reads it yet; the validation reusable workflow on the validation-framework branch will start fetching this file from main in a follow-up PR. Same content as the existing validation/config/validation-config.yaml minus fork_owners. Schema lives with the workflow code at the consuming ref (validation/schemas/validation-settings-schema.yaml on validation-framework). additionalProperties is true at every level so older callers can ignore fields added in newer schema revisions.
…m-validation chore: enable npm Dependabot for validation/ on validation-framework
…n-settings feat: seed config/validation-settings.yaml on main (refs camaraproject#226)
…rded-repos config: enable validation framework for onboarded repositories
Refresh the validation-framework copy of config/validation-settings.yaml with the 14 stage-enabled entries added on main via tooling#245, so the fallback configuration on this branch matches the live configuration on main. Also pulls in the npm/validation dependabot entry. Removes the main-side regression-runner.yml stub during the merge — VF's regression canaries live under different file names, so the stub is misleading here.
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
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?
repository management
What this PR does / why we need it:
Refreshes the validation-framework copy of
config/validation-settings.yamlto mirror the 14
stage: enabledentries added onmainvia tooling#245.Workflows read settings from
mainat runtime, but this branch holds thepinned-ref last-known-good fallback used by tagged releases — keeping it in
sync avoids stale fallback behavior if the runtime fetch from
maineverfails.
Also brings in the npm/
validation/Dependabot entry (added onmainviatooling#223) so VF participates in npm dependency tracking from this branch.
The merge removes
.github/workflows/regression-runner.ymlfrom this branch:the file is a stub on
mainwhose comment claims "the functional workflowlives on the
validation-frameworkbranch", but VF's regression canarieslive under different filenames (
validation-regression.ymlandrelease-automation-regression.yml). The stub is misleading on VF andserves no purpose here.
Which issue(s) this PR fixes:
N/A — operational refresh.
Special notes for reviewers:
Standard merge of
mainintovalidation-framework. One conflict(
config/validation-settings.yaml, add/add) resolved by keeping VF'sfallback explanatory comment block plus main's full repository list; one
stub removed (
regression-runner.yml, see above). Other main-side filesauto-merged.
Changelog input
Additional documentation