Repository navigation
fix(ci): run the validation canary on linting/** changes - #530
Merged
Merged
Conversation
Kevsy
approved these changes
Nov 10, 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?
What this PR does / why we need it:
The Validation Regression canary runs on pushes to
mainfiltered by path, and the filter listsvalidation/**but notlinting/**, where the Spectral rulesets and custom functions live. A ruleset-only change therefore moves tov1-rcwithout a canary run, although the regression fixtures exist to catch exactly that. #526 was only exercised because it also touched a test file. This PR addslinting/**to the filter and nameslinting/in the canary row of the tag-move gate table inbranching-model.md.Which issue(s) this PR fixes:
None.
Special notes for reviewers:
Workflow trigger and documentation only; no job logic changes. The push of this PR's merge will itself trigger a canary run.
Changelog input
Additional documentation