[gimlichael]

This pull request fixes module unload mutex collisions between unrelated coverage sessions and records the fix in the changelog as release 10.1.1. Hit files are now used as the mutex name in full, so sessions whose assembly names share a prefix no longer block one another.

Unload mutex fix:

• The unload mutex is named from the complete hit file name, including the session GUID and last namespace segment, instead of the name with its extension stripped.
• Unrelated modules and runtimes no longer serialize on a shared mutex through a common assembly-name prefix.
• A regression test holds a mutex under the legacy prefix name and verifies that the unload completes and the hit data is written.

Changelog:

• A 10.1.1 patch entry describes the mutex fix for users upgrading from 10.1.0.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The reviewed changes appear safe to merge, with no new blocking issues found.

Summary

Names the unload mutex from the complete hit-file name, keeping unrelated coverage sessions separate.

• Unrelated coverage sessions use separate unload mutexes.
• Coverlet packages use updated .NET runtime and Pkcs versions.
• Ubuntu CI jobs now run on Ubuntu 26.04.

No new actionable issues were found in the changes since the previous review. No previous review threads were supplied. Tests were not run.

_{Reviews (4) · Last reviewed commit: "✅ read runtime package versions from cen..." · Reviewed by Greptile}