Skip to content

Signed MSIX releases with Azure Artifact Signing (v2.0.0) - #6

Merged
edwest19 merged 2 commits into
mainfrom
release/signed-msix
Nov 6, 2026
Merged

edwest19 merged 2 commits into
mainfrom
release/signed-msix

Conversation

@edwest19

@edwest19 edwest19 commented Nov 6, 2026

Copy link
Copy Markdown
Owner

What this does

Sets up signed MSIX releases, ready for v2.0.0. Merging this publishes nothing: a release only starts when you push a version tag, and signing waits for your approval.

It combines your two proven setups:

  • Release design from SecretPrinter. Three separate jobs (build, sign, release), each with only the permission it needs. Actions are pinned to exact commits. The tag must match the version and the CHANGELOG. The signer's name is checked after signing.
  • MSIX packaging from SecretCsv. winapp pack, signed with CodeSigning-Apps on account edwest19 (East US).

How a release runs (.github/workflows/release.yml)

Job Can do What it does
build read the repo Checks the tag against the version, manifest and CHANGELOG; runs the tests; packages a self-contained x64 MSIX, unsigned
sign reach Azure signing, after your approval in environment release Signs the MSIX with Artifact Signing over OpenID Connect (no stored password). Checks it's valid, timestamped and signed as CN=Edwin West, O=Edwin West, L=Huntington, S=ny, C=US. Records its SHA-256.
release write the GitHub Release only Publishes SecretKey-X.Y.Z-x64.msix and its .sha256, with the CHANGELOG entry as the release notes

Other changes

  • Manifest:

    • Publisher is the exact signer name. It's case-sensitive (S=ny), as SecretCsv learned.
    • The version is 2.0.0.0.
    • The app is named SecretKey, published by Edwin West.
  • Version is in Directory.Build.props (2.0.0), and there's a new CHANGELOG.md with the 2.0.0 entry.

    • Its date is today, so edit it if you tag on another day.
  • build.yml: actions are pinned, and every pull request now packages the unsigned MSIX. If packaging breaks, you'll see it here, not at release time.

  • SecretKey.slnx: dropped package.pfx, which never existed.

  • New ReleaseRulesTests:

    • the publisher matches the signer
    • the three versions agree
    • the CHANGELOG has an entry for the version
    • every action is pinned
    • every file the solution lists exists
    • the README's release facts match the workflow

    Each was shown to fail when its rule is broken.

  • README: new Install and Releases sections. CLAUDE.md: rule 8, releases only through the workflow.

Before the first release: setup only you can do

  1. Azure. Create app registration SecretKey-GitHubActions-Signing, with a federated credential:

    • Scenario: GitHub actions deploying Azure resources
    • Organization: edwest19
    • Repository: SecretKey
    • Entity: Environment
    • Environment name: release

    Give it the Artifact Signing Certificate Profile Signer role, the same way SecretPrinter's registration has it.

  2. GitHub (SecretKey → Settings → Environments → release).

    • Required reviewer: you.
    • Deployment tags: v*.
    • Environment secrets:
      • AZURE_CLIENT_ID: the new registration's Application (client) ID
      • AZURE_TENANT_ID: same as SecretPrinter's
      • AZURE_SUBSCRIPTION_ID: same as SecretPrinter's

Then push v2.0.0-rc.1 for a signed pre-release to test, and v2.0.0 when you're happy.

How it was checked

  • 109 tests pass with a local stand-in runner. The test check below is the real MSTest run.
  • Both workflows pass actionlint.
  • The pinned commits were each checked against their version tags.
  • First-run unknowns:
    • the build check below is the first time winapp pack packages SecretKey
    • signing can only be tested by the first -rc tag, after the setup above

Generated by Claude Code

- release.yml: on a vX.Y.Z (or vX.Y.Z-rc.N) tag, three jobs.
  - build (read-only): checks the tag against Directory.Build.props,
    the manifest and CHANGELOG.md; tests; packages a self-contained,
    unsigned x64 MSIX with winapp.
  - sign (environment "release", OIDC, no stored secret): signs with
    account edwest19, profile CodeSigning-Apps (East US); checks the
    signature is valid, timestamped and made by EXPECTED_SIGNER;
    records SHA-256.
  - release (contents: write only): publishes the GitHub Release.
  Design follows SecretPrinter; packaging follows SecretCsv. Actions
  are pinned to the commits SecretPrinter uses, checked against tags.
- build.yml: actions pinned; every pull request now also packages the
  unsigned MSIX, so packaging problems surface before a tag.
- Manifest: Publisher = the verified signer name (case-sensitive,
  S=ny), Version 2.0.0.0, display name SecretKey, publisher Edwin West.
- Directory.Build.props (Version 2.0.0) and CHANGELOG.md added.
- package.pfx removed from SecretKey.slnx (it never existed).
- ReleaseRulesTests: publisher matches the signer, versions agree,
  changelog entry exists, actions pinned, solution files exist, and
  README's release facts match the workflow.
- README: Install and Releases sections. CLAUDE.md: rule 8 (releases
  only through the workflow), layout and claims map.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QSQZn3X5gDJdRjbqMfKRpd
- scripts/Test-Msix.ps1: fails unless the MSIX has the expected
  publisher and version, depends on no other package (self-contained),
  contains the app, SecretKey.Core and the .NET runtime, and asks for
  no permission except runFullTrust. Run by build.yml on every pull
  request and by release.yml before signing.
- Both workflows set DOTNET_CLI_TELEMETRY_OPTOUT=1 and
  WINAPP_CLI_TELEMETRY_OPTOUT=1 (winapp only checks for "1", per its
  source).
- README, CLAUDE.md and the solution list the script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QSQZn3X5gDJdRjbqMfKRpd
@edwest19
edwest19 merged commit 59bf0b8 into main Nov 6, 2026
2 checks passed
@edwest19
edwest19 deleted the release/signed-msix branch November 6, 2026 03:16
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.

2 participants