Bump the testing group with 3 updates by dependabot[bot] · Pull Request #907 · guibranco/CrispyWaffle

dependabot · 2026-04-24T14:57:57Z

Updated coverlet.msbuild from 8.0.1 to 10.0.0.

Release notes

Sourced from coverlet.msbuild's releases.

10.0.0 Improvements

Unique Report Filenames (coverlet.MTP and AzDO) #1866
Add --coverlet-file-prefix option for unique report files #1869
Introduce .NET 10 support #1823

Fixed

Fix [BUG] Wrong branch rate on IAsyncEnumerable for generic type #1836
Fix [BUG] Missing Coverage after moving to MTP #1843
Fix [BUG] No coverage reported when targeting .NET Framework with 8.0.1 #1842
Fix [BUG] Behavior changes between MTP and Legacy (msbuild) #1878
Fix [BUG] Coverlet.MTP - Unable to load coverlet.mtp.appsettings.json #1880
Fix [BUG] Coverlet.Collector produces empty report when Mediator.SourceGenerator is referenced #1718 by https://github.com/yusyd
Fix [BUG] Crash during instrumentation (Methods using LibraryImport/DllImport have no body) #1762

Maintenance

Add comprehensive async method tests and documentation for issue #1864
Replace Tmds.ExecFunction Package in coverlet.core.coverage.tests #1833
Add net9.0 and net10.0 targets #1822

Diff between 8.0.1 and 10.0.0

Commits viewable in compare view.

Updated FluentAssertions from 8.8.0 to 8.9.0.

Release notes

Sourced from FluentAssertions's releases.

8.9.0 What's Changed

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.3.0 to 18.4.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.4.0 What's Changed

Add LoongArch64 support by @stdmnpkg in Add LoongArch64 support microsoft/vstest#15359
Refactor Condition evaluation by @Youssef1313 in Refactor Condition evaluation microsoft/vstest#15357
Adding info on extensions points part 1 by @nohwnd in Adding info on extensions points part 1 microsoft/vstest#15360
Add option to ask for uploading code QL before the standard window ends by @nohwnd in Add option to ask for uploading code QL before the standard window ends microsoft/vstest#15373
Update runtime versions by @nohwnd in Update runtime versions microsoft/vstest#15372
Fix .NET 10 regression for traits by @Youssef1313 in Fix .NET 10 regression for traits microsoft/vstest#15370
Update target frameworks to net10.0 and net11.0 by @dotnet-maestro[bot] in Update target frameworks to net10.0 and net11.0 microsoft/vstest#15349
Fix names in pipeline matrix so we don't have to align them by @nohwnd in Fix names in pipeline matrix so we don't have to align them microsoft/vstest#15365
Update SECURITY.md by @Youssef1313 in Update SECURITY.md microsoft/vstest#15342

New Contributors

@stdmnpkg made their first contribution in Add LoongArch64 support microsoft/vstest#15359

Full Changelog: microsoft/vstest@v18.3.0...v18.4.0

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps coverlet.msbuild from 8.0.1 to 10.0.0 Bumps FluentAssertions from 8.8.0 to 8.9.0 Bumps Microsoft.NET.Test.Sdk from 18.3.0 to 18.4.0 --- updated-dependencies: - dependency-name: coverlet.msbuild dependency-version: 10.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: testing - dependency-name: FluentAssertions dependency-version: 8.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: testing - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: testing ... Signed-off-by: dependabot[bot] <support@github.com>

guibranco

Automatically approved by gstraccini[bot]

socket-security · 2026-04-24T14:58:25Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	nuget/coverlet.msbuild@8.0.1 ⏵ 10.0.0	^-32
	nuget/fluentassertions@8.8.0 ⏵ 8.9.0	⁺⁴
	nuget/microsoft.net.test.sdk@18.3.0 ⏵ 18.4.0

View full report

socket-security · 2026-04-24T14:58:27Z

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Block		System shell access: nuget `coverlet.msbuild` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/coverlet.msbuild@10.0.0` ℹ Read more on: This package \| This alert \| What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/coverlet.msbuild@10.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Dynamic code execution: nuget `coverlet.msbuild` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/coverlet.msbuild@10.0.0` ℹ Read more on: This package \| This alert \| What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/coverlet.msbuild@10.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Network access: nuget `microsoft.codecoverage` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.codecoverage@18.4.0` ℹ Read more on: This package \| This alert \| What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.codecoverage@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		System shell access: nuget `microsoft.codecoverage` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.codecoverage@18.4.0` ℹ Read more on: This package \| This alert \| What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.codecoverage@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Dynamic code execution: nuget `microsoft.codecoverage` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.codecoverage@18.4.0` ℹ Read more on: This package \| This alert \| What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.codecoverage@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		System shell access: nuget `microsoft.testplatform.objectmodel` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.objectmodel@18.4.0` ℹ Read more on: This package \| This alert \| What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.objectmodel@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Dynamic code execution: nuget `microsoft.testplatform.objectmodel` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.objectmodel@18.4.0` ℹ Read more on: This package \| This alert \| What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.objectmodel@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Network access: nuget `microsoft.testplatform.testhost` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.testhost@18.4.0` ℹ Read more on: This package \| This alert \| What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.testhost@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		System shell access: nuget `microsoft.testplatform.testhost` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.testhost@18.4.0` ℹ Read more on: This package \| This alert \| What is shell access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.testhost@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Dynamic code execution: nuget `microsoft.testplatform.testhost` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.testhost@18.4.0` ℹ Read more on: This package \| This alert \| What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.testhost@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: nuget `coverlet.msbuild` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/coverlet.msbuild@10.0.0` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/coverlet.msbuild@10.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: nuget `microsoft.codecoverage` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.codecoverage@18.4.0` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.codecoverage@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Potential code anomaly (AI signal): nuget `microsoft.codecoverage` is 100.0% likely to have a medium risk anomaly Notes: This C# assembly functions as a dynamic loader and interop wrapper for Microsoft DiaSymReader, with multiple loading paths (direct native DLLs, an environment-controlled alt path, and COM fallback). The primary security risk stems from environment-driven native library loading, which can be abused to execute attacker-controlled binaries. Mitigations should include: restricting and validating the alt-load path, verifying digital signatures or hashes of native binaries before loading, and avoiding SkipVerification unless strictly necessary. The COM fallback also warrants caution to ensure trusted COM components are used. Overall, moderate supply-chain risk due to load-path flexibility; no definitive malware detected within this fragment. Confidence: 1.00 Severity: 0.60 From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.codecoverage@18.4.0` ℹ Read more on: This package \| This alert \| What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.codecoverage@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: nuget `microsoft.testplatform.objectmodel` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.objectmodel@18.4.0` ℹ Read more on: This package \| This alert \| What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.objectmodel@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: nuget `microsoft.testplatform.objectmodel` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.objectmodel@18.4.0` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.objectmodel@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: nuget `microsoft.testplatform.testhost` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.testhost@18.4.0` ℹ Read more on: This package \| This alert \| What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.testhost@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Filesystem access: nuget `microsoft.testplatform.testhost` Location: Package overview From: Tests/CrispyWaffle.I18n.PtBr.Tests/CrispyWaffle.I18n.PtBr.Tests.csproj → `nuget/microsoft.net.test.sdk@18.4.0` → `nuget/microsoft.testplatform.testhost@18.4.0` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore nuget/microsoft.testplatform.testhost@18.4.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

github-actions · 2026-04-24T14:58:35Z

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-04-24T14:58:33Z INF scanning for exposed secrets...
2:58PM INF 799 commits scanned.
2026-04-24T14:58:34Z INF scan completed in 1.16s
2026-04-24T14:58:34Z INF no leaks found

sonarqubecloud · 2026-04-24T15:01:36Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

dependabot · 2026-04-24T15:35:47Z

Superseded by #908.

AppVeyorBot · 2026-04-24T15:38:41Z

❌ Build CrispyWaffle 10.0.1570 failed (commit 5cd547b73c by @dependabot[bot])

dependabot Bot assigned guibranco Apr 24, 2026

dependabot Bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file nuget packages labels Apr 24, 2026

guibranco enabled auto-merge (squash) April 24, 2026 14:58

gstraccini Bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label Apr 24, 2026

github-actions Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 24, 2026

gstraccini Bot approved these changes Apr 24, 2026

View reviewed changes

guibranco approved these changes Apr 24, 2026

View reviewed changes

gstraccini Bot added the 🤖 bot Automated processes or integrations label Apr 24, 2026

dependabot Bot closed this Apr 24, 2026

auto-merge was automatically disabled April 24, 2026 15:35
Pull request was closed

dependabot Bot deleted the dependabot/nuget/testing-97f5804b09 branch April 24, 2026 15:35

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the testing group with 3 updates#907

Bump the testing group with 3 updates#907
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/testing-97f5804b09

dependabot Bot commented on behalf of github Apr 24, 2026

Uh oh!

guibranco left a comment

Uh oh!

socket-security Bot commented Apr 24, 2026

Uh oh!

socket-security Bot commented Apr 24, 2026

Uh oh!

github-actions Bot commented Apr 24, 2026

Uh oh!

sonarqubecloud Bot commented Apr 24, 2026

Uh oh!

dependabot Bot commented on behalf of github Apr 24, 2026

Uh oh!

AppVeyorBot commented Apr 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

dependabot Bot commented on behalf of github Apr 24, 2026

10.0.0

Improvements

Fixed

Maintenance

8.9.0

What's Changed

New features

Improvements

Fixes

Documentation

Others

18.4.0

What's Changed

New Contributors

Uh oh!

guibranco left a comment

Choose a reason for hiding this comment

Uh oh!

socket-security Bot commented Apr 24, 2026

Uh oh!

socket-security Bot commented Apr 24, 2026

Uh oh!

github-actions Bot commented Apr 24, 2026

Uh oh!

sonarqubecloud Bot commented Apr 24, 2026

Quality Gate passed

Uh oh!

dependabot Bot commented on behalf of github Apr 24, 2026

Uh oh!

AppVeyorBot commented Apr 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants