Enable strictChangefileValidation experiment#5783
Merged
iclanton merged 3 commits intomicrosoft:mainfrom Apr 18, 2026
Merged
Conversation
iclanton
requested review from
apostolisms,
bmiddha,
dmichon-msft and
jxanthony
as code owners
bmiddha
approved these changes
Apr 18, 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
2 participants
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.
Summary
strictChangefileValidationexperiment inexperiments.json, which causesrush change --verifyto report errors for change files that reference non-existent projects or target a lockstepped project that isn't the policy's main project.pnpm-config.jsonfrom the repo template.@rushstack/localization-plugin,@rushstack/tls-sync-vscode-shared,tls-sync-vscode-extension-pack), which would fail validation under the new strict mode.Test plan
rush change --verifypasses with the new experiment enabled🤖 Generated with Claude Code