fix(releases): Artifact Signing dependency conflicts with NuGet source mapping #43

Closed
opened 2026-10-12 20:49:14 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-12 20:49:14 +00:00 (Migrated from github.com)

The protected MarkdownViewr dev release reaches Azure through OIDC, then the official Artifact Signing v2 action fails installing its pinned Sign CLI because dotnet tool install --add-source cannot be combined with the caller NuGet.Config package source mapping.

Keep the caller package source policy intact. Prestage the exact official action dependency from nuget.org with a pinned SHA256 and NuGet signature verification; retain official action signing, publisher checks and final distributed-byte verification.

Evidence: https://github.com/KofTwentyTwo/MarkdownViewr.Windows/actions/runs/38299469062
Local reproduction matches the hosted error; real verified-package bootstrap succeeds. Regression boundaries cover changed downloads, invalid signatures, existing directories and missing executables.

The protected MarkdownViewr dev release reaches Azure through OIDC, then the official Artifact Signing v2 action fails installing its pinned Sign CLI because `dotnet tool install --add-source` cannot be combined with the caller NuGet.Config package source mapping. Keep the caller package source policy intact. Prestage the exact official action dependency from nuget.org with a pinned SHA256 and NuGet signature verification; retain official action signing, publisher checks and final distributed-byte verification. Evidence: https://github.com/KofTwentyTwo/MarkdownViewr.Windows/actions/runs/38299469062 Local reproduction matches the hosted error; real verified-package bootstrap succeeds. Regression boundaries cover changed downloads, invalid signatures, existing directories and missing executables.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/standards#43