-
Notifications
You must be signed in to change notification settings - Fork 133
Disable roll-forward to fix spontaneous CI build failure. #826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
See https://github.com/CommunityToolkit/Windows/actions/runs/21039291527/job/60496336547 Error observed is: ``` 6>CSC : error CS8032: An instance of analyzer Microsoft.CodeAnalysis.UseExplicitTupleName.UseExplicitTupleNameDiagnosticAnalyzer cannot be created from C:\Program Files\dotnet\sdk\9.0.309\Sdks\Microsoft.NET.Sdk\codestyle\cs\Microsoft.CodeAnalysis.CodeStyle.dll : Exception has been thrown by the target of an invocation.. [D:\a\Labs-Windows\Labs-Windows\tooling\CommunityToolkit.Tooling.TestGen\CommunityToolkit.Tooling.TestGen.csproj] ```
Member
Author
michael-hawker
approved these changes
Jan 15, 2026
Member
|
From other PR linking to the underlying Roslyn issue here: dotnet/roslyn#82010 |
Arlodotexe
added a commit
that referenced
this pull request
Feb 2, 2026
- Update SDK version from 9.0.308 to 9.0.310 in global.json - Reorder workflow steps: checkout before setup-dotnet - Use global-json-file input for jobs with checkout - Maintain DOTNET_VERSION env var for artifact-only jobs (no checkout) This eliminates version duplication and prevents future drift between global.json and workflow definitions. Related to PR #826 which disabled rollForward to prevent SDK version mismatches.
Arlodotexe
added a commit
that referenced
this pull request
Feb 2, 2026
- Update SDK version from 9.0.308 to 9.0.310 in global.json - Reorder workflow steps: checkout before setup-dotnet - Use global-json-file input for jobs with checkout - Maintain DOTNET_VERSION env var for artifact-only jobs (no checkout) This eliminates version duplication and prevents future drift between global.json and workflow definitions. Related to PR #826 which disabled rollForward to prevent SDK version mismatches.
Arlodotexe
added a commit
that referenced
this pull request
Feb 2, 2026
- Update SDK version from 9.0.308 to 9.0.310 in global.json - Reorder workflow steps: checkout before setup-dotnet - Use global-json-file input for jobs with checkout - Maintain DOTNET_VERSION env var for artifact-only jobs (no checkout) This eliminates version duplication and prevents future drift between global.json and workflow definitions. Related to PR #826 which disabled rollForward to prevent SDK version mismatches.
Arlodotexe
added a commit
that referenced
this pull request
Feb 2, 2026
- Update SDK version from 9.0.308 to 9.0.310 in global.json - Reorder workflow steps: checkout before setup-dotnet - Use global-json-file input for jobs with checkout - Maintain DOTNET_VERSION env var for artifact-only jobs (no checkout) This eliminates version duplication and prevents future drift between global.json and workflow definitions. Related to PR #826 which disabled rollForward to prevent SDK version mismatches.
Arlodotexe
added a commit
that referenced
this pull request
Feb 3, 2026
- Update SDK version from 9.0.308 to 9.0.310 in global.json - Reorder workflow steps: checkout before setup-dotnet - Use global-json-file input for jobs with checkout - Maintain DOTNET_VERSION env var for artifact-only jobs (no checkout) This eliminates version duplication and prevents future drift between global.json and workflow definitions. Related to PR #826 which disabled rollForward to prevent SDK version mismatches.
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.
See https://github.com/CommunityToolkit/Windows/actions/runs/21039291527/job/60496336547
Error observed is:
Fixes
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Other information