Repository navigation
fix(ci): run mutation testing natively with the configured .NET SDKs - #1108
Merged
Merged
Conversation
This was referenced Nov 17, 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.
Problem
mutation-dotnet.ymlruns Stryker.NET through a Docker-based action whose image is fixed tomcr.microsoft.com/dotnet/sdk:10.0. Solutions that target a newer SDK (for examplenet11.0) cannot be evaluated: Stryker reportsNETSDK1045,simulated build failedfor every project and finallyoverall analysis failed hence can't be mutated.Failing run in a consumer repository: https://github.com/dailydevops/schemas/actions/runs/43994541132
Change
dotnetVersioninput with the same name and default (10.x/11.x) asbuild-dotnet-single.yml.actions/setup-dotnet(same pinned SHA as the other workflows) and rundotnet-stryker5.0.0 (the version the previous action image shipped) natively as a global tool.configurationFileinput, theSTRYKER_DASHBOARD_API_KEYsecret and the HTML report artifact upload unchanged.Compatibility
Inputs, secrets and artifact names are unchanged;
dotnetVersionis optional. The reusable workflow had no outputs, so none are lost. Callers now get SDKs 10.x and 11.x by default; callers that need others passdotnetVersion. The old action'sstrykerArgswas never exposed by this workflow.Verification
Dispatched a throwaway workflow in a consumer repository (on a temporary branch, since deleted) that called this branch: the run succeeded, including setup, Stryker run, step summary and report upload (https://github.com/dailydevops/schemas/actions/runs/43997079777). Stryker still logs
simulated build failed. Trying again with a nuget restore.warnings per project, but recovers and completes, unlike before. The dashboard upload itself and the exact content of the step summary were not inspected by me.actwas not available.To test: call the workflow from a repository with a
net11.0target and astryker-config.json, referencing this branch, and dispatch it.