Skip to content

Require code signing for releases; bump setup-msbuild to v3#355

Merged
erikdarlingdata merged 1 commit into
devfrom
fix/require-signing
Jun 2, 2026
Merged

Require code signing for releases; bump setup-msbuild to v3#355
erikdarlingdata merged 1 commit into
devfrom
fix/require-signing

Conversation

@erikdarlingdata

Copy link
Copy Markdown
Owner

@-

The signing step previously degraded to unsigned binaries when
SIGNPATH_API_TOKEN was absent, only emitting a ::warning::. Two problems:

- A genuinely missing/broken token would silently ship unsigned binaries
  and the release would still succeed — discovered only via user SmartScreen
  reports.
- Because GitHub echoes the full run: script into the log, the literal
  "releasing unsigned binaries" text appears in every run's log regardless
  of which branch executes, making `grep`-ing the log for signing status
  misleading (the warning never actually fired on signed releases).

Make signing required instead: if the token is missing the job fails loudly
(::error:: + exit 1). The Upload/Sign/Replace steps now run unconditionally
(this workflow only fires on maintainer dev->main release merges, where the
secret is always available). Secret is read via env: rather than inline
${{ }} interpolation into the script.

Also bump microsoft/setup-msbuild@v2 -> @V3 to move off the deprecated
Node 20 runtime (v3 runs on Node 24).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@erikdarlingdata erikdarlingdata merged commit 16c4bbf into dev Jun 2, 2026
2 checks passed
@erikdarlingdata erikdarlingdata deleted the fix/require-signing branch June 2, 2026 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant