[dotnet] Add new mlaunch 1.1.127 assemblies to SignList.xml#25745
[dotnet] Add new mlaunch 1.1.127 assemblies to SignList.xml#25745dalexsoto wants to merge 1 commit into
Conversation
The mlaunch bump from 1.1.113 to 1.1.127 (Xcode 27.0 Beta 1 baseline, #25729) added new assemblies to mlaunch.app/Contents/MonoBundle: the Microsoft.Testing.Platform managed assembly + localized satellites, and a few architecture-specific (R2R) runtime assemblies under .xamarin/<rid>/ (System.ComponentModel, System.Private.Xml.Linq, System.Text.Encodings.Web, System.Threading and System.Xml.Linq). These new files are not classified in SignList.xml, so the MicroBuild signing step in the "Prepare .NET Release" stage fails with "unknown files which should be signed" (HandleUnmappedFiles=fail). Add the 7 new assemblies as FirstParty so they are signed, consistent with the rest of the mlaunch.app MonoBundle content. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the signing manifest to classify newly introduced mlaunch.app managed assemblies as FirstParty, ensuring the MicroBuild signing step doesn’t fail due to unmapped files after the Microsoft.Tools.Mlaunch NuGet bump.
Changes:
- Add
Microsoft.Testing.Platform(and its.resources) assemblies toFirstParty. - Add additional runtime assemblies (
System.*) introduced under.xamarin/<rid>/toFirstParty.
✅ [PR Build #4576007] Build passed (Detect API changes) ✅Pipeline on Agent |
This comment has been minimized.
This comment has been minimized.
✅ [PR Build #4576007] Build passed (Build packages) ✅Pipeline on Agent |
✅ API diff for current PR / commitNET (empty diffs)✅ API diff vs stableNET (empty diffs)ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
✅ [PR Build #4576007] Build passed (Build macOS tests) ✅Pipeline on Agent |
🔥 [CI Build #4576007] Test results 🔥Test results❌ Tests failed on VSTS: test results 0 tests crashed, 2 tests failed, 206 tests passed. Failures❌ linker tests (iOS)1 tests failed, 14 tests passed.Failed tests
Html Report (VSDrops) Download ❌ monotouch tests (iOS)1 tests failed, 18 tests passed.Failed tests
Html Report (VSDrops) Download Successes✅ assembly-processing: All 1 tests passed. Html Report (VSDrops) Download macOS tests✅ Tests on macOS Sonoma (14): All 5 tests passed. Html Report (VSDrops) Download Linux Build VerificationPipeline on Agent |
The mlaunch bump from 1.1.113 to 1.1.127 (Xcode 27.0 Beta 1 baseline, #25729) added new assemblies to mlaunch.app/Contents/MonoBundle: the Microsoft.Testing.Platform managed assembly + localized satellites, and a few architecture-specific (R2R) runtime assemblies under .xamarin// (System.ComponentModel, System.Private.Xml.Linq, System.Text.Encodings.Web, System.Threading and System.Xml.Linq).
These new files are not classified in SignList.xml, so the MicroBuild signing step in the "Prepare .NET Release" stage fails with "unknown files which should be signed" (HandleUnmappedFiles=fail).
Add the 7 new assemblies as FirstParty so they are signed, consistent with the rest of the mlaunch.app MonoBundle content.