Repository navigation
NOISSUE - disable riscv64 builds for manager and proxy - #229
Merged
dborovcanin merged 1 commit intoJun 8, 2026
Merged
Conversation
dborovcanin
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This is a bug fix because it temporarily disables riscv64 builds for manager and proxy until wasmtime-go adds riscv64 support: bytecodealliance/wasmtime-go#285
What does this do?
Removes `linux/riscv64` from the build matrix and Docker platforms for `manager` and `proxy`. The `cli` service is unaffected since it has no wasmtime-go dependency. Both `build.yml` (binary matrix) and `cd.yml` (Docker multi-arch platforms) are updated.
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
No — this is a CI configuration change only.
Did you document any new/modified features?
No. This is a temporary workaround; revert once wasmtime-go cuts a release with riscv64 support.