[dependabot]

Updated Microsoft.CodeAnalysis.CSharp.Analyzer.Testing from 1.1.3-beta1.26255.1 to 1.1.4.

Release notes

Sourced from Microsoft.CodeAnalysis.CSharp.Analyzer.Testing's releases.

No release notes found for this version range.

Commits viewable in compare view.

[Copilot]

One or more custom setup steps configured for this repository failed during this Copilot code review run:

Build the repository

Setup steps run before each review. If the review above is missing context, or no review was posted at all, the failing step above may be the cause. See the workflow run for failure details, fix your setup steps configuration, and re-request a review.

Note

You can configure setup steps for Copilot code review separately from Copilot cloud agent with a copilot-code-review.yml file. Read the docs for details.

[Copilot]

🟢 Approval recommended

No active review issues remain for the dependency update, though build and test compatibility have not been verified.

No open issues 🎉

What changed in this PR

Updates the centrally managed Roslyn analyzer-testing dependency used by TestFx’s test infrastructure.

Changes:

• Bumps MicrosoftCodeAnalysisAnalyzerTestingVersion from 1.1.3-beta1.26255.1 to stable version 1.1.4.
• Makes no source or test-code changes.

Validation is limited to the supplied diff; build and test compatibility were not verified.

File	Description
Directory.Packages.props	Updates the shared analyzer-testing package version to 1.1.4.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The six Bazel analyzer-testing packages remain pinned to 1.1.3-beta1.26255.1 while MSBuild moves to 1.1.4, leaving the test lanes on inconsistent library versions.

1 open issue

• Update Bazel analyzer-testing package pins to 1.1.4 · New

_{Review effort: Balanced}

[Copilot]

One or more custom setup steps configured for this repository failed during this Copilot code review run:

Build the repository

Setup steps run before each review. If the review above is missing context, or no review was posted at all, the failing step above may be the cause. See the workflow run for failure details, fix your setup steps configuration, and re-request a review.

Note

You can configure setup steps for Copilot code review separately from Copilot cloud agent with a copilot-code-review.yml file. Read the docs for details.

[github-actions]

Final test-triage resolution — Azure Pipelines build 1674966

No test failures were found in this build, so no issue is warranted.

• Evidence was complete (evidenceIncomplete: false). The collector found 0 test results, 0 failures or retries, 0 slow tests and 0 crash or hang diagnostics.
• The failed legs (Windows Debug, Linux Release, WindowsSamples Release, and the "Validate affected-test rollout" step) failed in the Build or Build Samples steps, not in tests. The Build error is NU1103: no stable package found for Microsoft.CodeAnalysis.VisualBasic... in MSTest.Analyzers.UnitTests.
• Because the build failed, no TRX files were produced, so tests did not run. This does not show the tests are clean.
• Build failures belong to Build Failure Analysis. Fix the NU1103 package resolution error first, then re-run the pipeline so tests can execute.

Confidence: high that this is a build and restore failure, not a test failure.

🤖 Automated content by GitHub Copilot. Generated by the Pipeline Test Triage workflow. · copilot · auto · ~20 AIC · ⌖ ~1 AIC · ⊞ 10.1K

[Amaury Levé (Evangelink)]

Superseded by #12344. These PRs all change the same shared Roslyn testing version property to 1.1.4. #12344 includes the six Bazel pins, regenerated lock/integrity metadata, and Dependabot grouping so this update is kept in one PR.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.