The composite action currently hard-codes review-bot-linux-amd64 as the binary name. If arm64 runners or other OS/arch combinations are used, the action will fail to find the correct binary.
Proposed Solution
Derive the asset name dynamically from uname -m / uname -s or accept an input parameter for the target architecture.
Context
Raised in review #3658 comment 21186 during PR #121 review. Deferred as out of scope for that PR (focused on VCS host detection and security hardening).
## Problem
The composite action currently hard-codes `review-bot-linux-amd64` as the binary name. If arm64 runners or other OS/arch combinations are used, the action will fail to find the correct binary.
## Proposed Solution
Derive the asset name dynamically from `uname -m` / `uname -s` or accept an input parameter for the target architecture.
## Context
Raised in review [#3658 comment 21186](https://gitea.weiker.me/rodin/review-bot/pulls/121#issuecomment-21186) during PR #121 review. Deferred as out of scope for that PR (focused on VCS host detection and security hardening).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The composite action currently hard-codes
review-bot-linux-amd64as the binary name. If arm64 runners or other OS/arch combinations are used, the action will fail to find the correct binary.Proposed Solution
Derive the asset name dynamically from
uname -m/uname -sor accept an input parameter for the target architecture.Context
Raised in review #3658 comment 21186 during PR #121 review. Deferred as out of scope for that PR (focused on VCS host detection and security hardening).