check-version: survive the deprecated/ layout transition on the main side - #1821
Merged
Merged
Conversation
…en deprecated/ is absent Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The version-bump check reads MAIN's Dashboard.csproj to compare against the PR's, but only at the new deprecated/ path — which doesn't exist on main until the v3.3.0 promotion itself merges. Release PR #1820 therefore failed check-version on a path error, not a version verdict. Falls back to the pre-move location; removable once main carries the new layout. (check-version is not a required context; this is correctness + optics for the release PR.)
🤖 Generated with Claude Code