Fix Windows arm64 release: use forked setup-sentry-cli with win32/arm64 mapping

[advait-m]

Description

The Bundle Release (Windows arm64) job fails at the Set up Sentry CLI step:

Installing sentry-cli version latest
Error: TypeError: Unsupported platform: win32/arm64

(failing job)

Root cause. matbour/setup-sentry-cli picks a sentry-cli asset from a hardcoded table with no win32-arm64 entry, and its only fallback covers darwin:

const PLATFORM_MAPPINGS: Record<string, string> = {
  ...
  'win32-x32': 'Windows-i686',
  'win32-x64': 'Windows-x86_64',   // no 'win32-arm64'
};
...
throw new TypeError(`Unsupported platform: ${process.platform}/${process.arch}`);

This started with #27746, which moved the Windows arm64 release legs from windows-latest-large onto the native windows-arm-latest-large runner. Previously the action ran on an x64 host cross-compiling to arm64, so Node reported win32/x64 and it worked. Now it reports win32/arm64.

Everything before this step — build, Azure Trusted Signing, Inno Setup bundling — succeeds. The job only dies setting up the Sentry CLI, which then skips the symbol upload, the GitHub release asset upload, and the GCS upload.

Fix. sentry-cli does publish sentry-cli-Windows-aarch64.exe, so only the action's mapping is stale. Rather than working around it locally, the mapping is fixed at the source and we consume it via a fork until upstream ships it:

• Upstream PR: fix(arch): add support for Windows arm64 matbour/setup-sentry-cli#24 — adds 'win32-arm64': 'Windows-aarch64', mirroring the existing linux-arm64 → Linux-aarch64 entry.
• Fork: warpdotdev/setup-sentry-cli, which is upstream main plus exactly that commit. This lives in warpdotdev alongside our other action dependencies (oz-agent-action, generate-changelog, repo-sync) rather than a personal account.

This PR just repoints the Windows call site at the fork, pinned by SHA per repo convention:

uses: warpdotdev/setup-sentry-cli@80a37ad0848719ac9d0390ee4197fd070af6718e # v2.0.0 + win32/arm64

Scope. Only the Windows call site moves. The other 8 (macOS, Linux, web) work fine on upstream, and leaving them there keeps currently-healthy release legs off a fork they don't need.

Reverting. Once matbour/setup-sentry-cli#24 lands and is released, this is a one-line change back to matbour/setup-sentry-cli@<new-sha>. There's a TEMPORARY: comment at the call site pointing at the upstream PR.

Linked Issue

N/A — CI/release-pipeline regression, no tracking issue.

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

Windows-runner-only CI change, so it can't be exercised via ./script/run. Verified as follows:

• The asset exists and is the right architecture. sentry-cli-Windows-aarch64.exe returns 200 from the Sentry CDN, and file reports PE32+ executable (console) Aarch64, for MS Windows (11.7 MB).
• The pinned SHA actually carries the fix. action.yml at 80a37ad runs dist/main.js, and that bundle contains all three Windows entries:

  "win32-x32": "Windows-i686"
  "win32-x64": "Windows-x86_64"
  "win32-arm64": "Windows-aarch64"
  

  This matters because dist/ is committed in that repo — a source-only change would have been inert.
• The fork's bundle is trustworthy. I confirmed dist/ rebuilds byte-for-byte from unmodified upstream main before applying the change, so the fork's bundle diff is purely the mapping entry and not build-environment drift. pnpm lint and pnpm typecheck pass there.
• Static checks here. Workflow YAML parses and the rewritten step resolves as expected; ./script/lint_powershell -ci exits 0.

Full end-to-end confirmation needs a dev release run on the arm64 runner, since the step is gated on should_publish == 'true'.

Screenshots / Videos

N/A — no user-visible surface.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

---

Warp conversation

[warp-for-oss]

@advait-m

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

Overview

This PR replaces matbour/setup-sentry-cli only for the Windows release job with a small PowerShell installer that selects the official Sentry CLI Windows asset from RUNNER_ARCH, adds it to PATH, and forwards the Sentry environment values needed by the existing upload script.

Concerns

No blocking correctness, security, testing, comment-quality, or spec-alignment concerns found. The added comments explain the third-party action compatibility workaround rather than narrating the implementation, and the PR is not user-visible so screenshots/videos are not required.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz