.github/workflows/release-windows.yml builds and publishes a Windows release. ADR 0005 says why MSIX, self-contained, Native AOT, Artifact Signing and winget. An agent runs these commands when the maintainer says to release; it never creates the tag on its own.
TablePro_X.Y.Z.0_x64_arm64.msixbundleon thewindows-vX.Y.ZGitHub release, withSHA256SUMS: the x64 and Arm64 MSIX in one bundle, signed with Azure Artifact Signing. Windows installs the package for its own architecture.- A pull request to microsoft/winget-pkgs that adds
TablePro.TableProX.Y.Z, sowinget install TablePro.TableProgets it once Microsoft merges it.
- A tag is
windows-vX.Y.Z, each number at most 65535. The package version isX.Y.Z.0. - There is no pre-release tag. MSIX orders versions by their four numbers, so a beta could not sort below its stable.
- The tag is the only place the version is written. The workflow sets it in
Package.appxmanifestand passes-p:Version, which Settings shows. A local build keeps the csproj's0.1.0.
The maintainer does these once, in this order: a tag runs the workflow file at the tagged commit, so the rulesets come before any secret. The workflow's header names the same secrets and variables. Until steps 1 to 5 are done, a run builds and checks unsigned packages and publishes nothing.
- Rulesets: add
windows-v*to the tag rulesets, so its tags never move and only admins create them (.claude/rules/ci.md, Required checks). - Artifact Signing: an Azure Artifact Signing account, its identity validation, and a Public Trust certificate profile (quickstart).
- An app registration with the Artifact Signing Certificate Profile Signer role on the account, and a federated credential for GitHub Actions: organization
TableProApp, repositoryTablePro, entity Environment, namewindows-release(Authenticating with OpenID Connect). - Environment
windows-release, deploying fromwindows-v*tags only, with a required reviewer, and the secretsAZURE_CLIENT_ID,AZURE_TENANT_IDandAZURE_SUBSCRIPTION_ID. - Repository variables:
WINDOWS_SIGNING_ENDPOINT: the account's regional endpoint, such ashttps://eus.codesigning.azure.net/.WINDOWS_SIGNING_ACCOUNTandWINDOWS_SIGNING_PROFILE: the account and its certificate profile.WINDOWS_PUBLISHER: the certificate profile's subject, exactly as the certificate shows it, such asCN=Name, O=Name, L=City, S=State, C=Country. The package's Publisher has to match it, or signing fails. It also fixes the package family name, and Windows takes a package with another publisher for another app, so it never changes after the first release.
- Environment
windows-winget, deploying fromwindows-v*tags only, with a required reviewer, and the secretWINGET_TOKEN: a classic token with thepublic_reposcope (wingetcreate, token). That scope writes to every public repository its account can, so the account is one outside TableProApp whose only use is its fork of microsoft/winget-pkgs.
-
Dry run. It builds, checks, installs and starts both packages as the tag does, and publishes nothing. With
-f sign=trueit signs too, oncewindows-releasealso allowsmain; never a branch pattern, since whoever writes the branch writes the workflow that runs with the signing secrets.gh workflow run release-windows.yml --ref main -f version=X.Y.Z
-
The tag, on a
maincommit whose CI push run is green and whosedeny.tomlignores no advisory on the grounds that Windows has no release:git fetch origin --tags gh run list --workflow ci.yml --branch main --event push --commit <commit> git tag -s windows-vX.Y.Z -m windows-vX.Y.Z <commit> git push origin windows-vX.Y.Z
-
The workflow,
gh run list --workflow release-windows.yml --limit 3:- Builds an MSIX per architecture: Release configuration, the core in Cargo's release profile, Native AOT. It fails when the package's version, architecture or Windows 10 1809 floor is wrong, when it depends on a framework package, when
TablePro.dllis in it, or when a binary in it imports the VC++ redistributable. - Bundles both and signs the bundle, which signs the packages in it. A reviewer approves the step.
- Installs the bundle on Windows Server 2022 (x64, build 20348, the oldest Windows a hosted runner has) and Windows 11 (Arm64), and runs
TheInstalledPackageStartsAndKeepsItsFilesInLocalStatefrom the UI tests on each, in light and dark. - Writes the winget manifest and runs
winget validateon it. - Publishes the GitHub release, which a reviewer approves. The repository's latest release stays the macOS one.
- Opens the winget-pkgs pull request with wingetcreate, which a reviewer approves.
- Builds an MSIX per architecture: Release configuration, the core in Cargo's release profile, Native AOT. It fails when the package's version, architecture or Windows 10 1809 floor is wrong, when it depends on a framework package, when
-
Afterwards: watch the winget-pkgs pull request. Its bots validate and install the package, and a label such as
Needs-Author-Feedbackwaits for an answer.
- Nothing reaches users before the GitHub release job. Tags never move: a code fix lands on
mainand ships as the next number. - A runner or network failure:
gh run rerun <run> --failed. - winget-pkgs rejects the pull request: fix
windows/ci/winget-manifest.pyonmain, run it on the published bundle with the family name the install step printed, and submit that folder withwingetcreate submit. The release stays as published.