Fix sentry-cli path on Windows Git Bash

[fernandotonon]

Summary

• The curl sentry-cli installer places the binary at /usr/local/bin/sentry-cli, which is not in Git Bash's PATH on Windows runners
• Use the full path /usr/local/bin/sentry-cli instead of just sentry-cli

Test plan

• Merge and verify Windows release build passes

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated deployment workflow configuration for improved reliability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6543792d-7883-4c33-9453-65399ea11ced

📥 Commits

Reviewing files that changed from the base of the PR and between 6588ce5 and 710e2e5.

📒 Files selected for processing (1)

• .github/workflows/deploy.yml

---

📝 Walkthrough

Walkthrough

The GitHub Actions deploy workflow is updated to invoke the sentry-cli binary using its absolute path (/usr/local/bin/sentry-cli) instead of relying on command-line PATH resolution when uploading debug files to Sentry.

Changes

Cohort / File(s)	Summary
Sentry CLI invocation .github/workflows/deploy.yml	Replaces relative sentry-cli command with absolute path /usr/local/bin/sentry-cli for debug file uploads.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Fix CI release build failures in Sentry debug symbol steps #175: Modifies Sentry debug-symbol upload configuration in the same workflow file, addressing sentry-cli invocation and PATH handling.

Poem

🐰 A path once lost in shadowed lands,
Now gleams in absolute commands,
No search through winding PATH we go,
Just /usr/local/bin—clear and true! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: using an absolute path for sentry-cli on Windows Git Bash instead of relying on PATH resolution.
Description check	✅ Passed	The description is missing the 'Technical Details' section with bullets of areas changed, and the checkboxes are incomplete. However, the Summary section is clear and the overall intent is understandable.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/windows-sentry-cli-path

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud