feat: Add Linux riscv64 support - #3396
Conversation
Build and distribute sentry-cli for Linux riscv64 across GitHub releases, npm, PyPI, and Homebrew. Leave package-lock.json unchanged because @sentry/cli-linux-riscv64 is not published yet.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 5f19c03. Configure here.
| "@sentry/cli-linux-arm": "3.6.2", | ||
| "@sentry/cli-linux-arm64": "3.6.2", | ||
| "@sentry/cli-linux-i686": "3.6.2", | ||
| "@sentry/cli-linux-riscv64": "3.6.2", |
There was a problem hiding this comment.
Lockfile missing new optional dependency
Medium Severity
@sentry/cli-linux-riscv64 was added to optionalDependencies without a matching package-lock.json entry. npm ci requires those files to stay in sync and already special-cases this mismatch on release branches, so Test Node and other npm ci --ignore-scripts jobs can fail until the lockfile includes the package.
Reviewed by Cursor Bugbot for commit 5f19c03. Configure here.


Description
Build and distribute sentry-cli for Linux riscv64 across GitHub releases, npm, PyPI, and Homebrew. Leave package-lock.json unchanged because @sentry/cli-linux-riscv64 is not published yet.
Issues
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.