From f6a12b3ec2dceaf75622087ad9c47c989c162496 Mon Sep 17 00:00:00 2001
From: "riseproject-dev[bot]"
 <330740410+riseproject-dev[bot]@users.noreply.github.com>
Date: Tue, 29 Sep 2026 08:01:56 +0000
Subject: [PATCH 1/2] nemo-relay: Add version 0.9.3

Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>
---
 docs/packages/nemo-relay.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/packages/nemo-relay.yaml b/docs/packages/nemo-relay.yaml
index 85678459808..ff6f5f94cca 100644
--- a/docs/packages/nemo-relay.yaml
+++ b/docs/packages/nemo-relay.yaml
@@ -30,3 +30,4 @@ versions:
   - filename: nemo_relay-0.9.2-cp311-abi3-manylinux_2_39_riscv64.whl
     sha256: 1bf0cde243c7835d9a5d1a5bdb4668a810fa80885e392cf5e7d2cefd7ef69990
     requires-python: '>=3.11'
+- version: 0.9.3

From ff4901319e92c52d36ad393455a692291434d365 Mon Sep 17 00:00:00 2001
From: Ludovic Henry <git@ludovic.dev>
Date: Thu, 1 Oct 2026 08:44:41 +0000
Subject: [PATCH 2/2] nemo-relay: carry forward riscv64 patch(es) to 0.9.3

The nightly-upgrade bot bumped docs/packages/nemo-relay.yaml to 0.9.3 without
creating a matching patches/nemo-relay/0.9.3/ directory, so the workflow's
unconditional 'git apply .../*.patch' step failed with no matching file.
Carrying forward the same patch(es) from 0.9.2/ unchanged; CI will
confirm they still apply cleanly against the new upstream version.
---
 ...l-back-to-prost-build-s-own-protoc-l.patch | 39 +++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 patches/nemo-relay/0.9.3/0001-worker-proto-fall-back-to-prost-build-s-own-protoc-l.patch

diff --git a/patches/nemo-relay/0.9.3/0001-worker-proto-fall-back-to-prost-build-s-own-protoc-l.patch b/patches/nemo-relay/0.9.3/0001-worker-proto-fall-back-to-prost-build-s-own-protoc-l.patch
new file mode 100644
index 00000000000..c1892394f22
--- /dev/null
+++ b/patches/nemo-relay/0.9.3/0001-worker-proto-fall-back-to-prost-build-s-own-protoc-l.patch
@@ -0,0 +1,39 @@
+From 7d7539c7e835dd8fd9cabd470748296a7a8bad72 Mon Sep 17 00:00:00 2001
+From: Ludovic Henry <git@ludovic.dev>
+Date: Sun, 6 Sep 2026 09:43:30 +0200
+Subject: [PATCH] worker-proto: fall back to prost-build's own protoc lookup on
+ riscv64
+
+Upstream-Status: Inappropriate [protoc-bin-vendored ships no riscv64 binary; prost_build::Config::new() already defaults protoc_executable to its own PROTOC-env/PATH lookup, so simply not overriding it on unsupported platforms is the whole fix]
+
+protoc_bin_vendored::protoc_bin_path() returns Err on any platform outside
+its small enum of prebuilt targets (x86, x86_64, aarch64, ppc64le, s390x,
+macOS, Windows), which the crate's build.rs propagated with ?, aborting
+the build before prost_build ever got a chance to look for a protoc on
+PATH or via $PROTOC. Only calling protoc_executable() when the vendored
+lookup succeeds restores that fallback, which is documented in
+prost-build's own "Sourcing protoc" section.
+
+Signed-off-by: Ludovic Henry <git@ludovic.dev>
+---
+ crates/worker-proto/build.rs | 7 ++++++-
+ 1 file changed, 6 insertions(+), 1 deletion(-)
+
+diff --git a/crates/worker-proto/build.rs b/crates/worker-proto/build.rs
+index 5fddbc74..888ec366 100644
+--- a/crates/worker-proto/build.rs
++++ b/crates/worker-proto/build.rs
+@@ -7,7 +7,12 @@ fn main() -> Result<(), Box<dyn std::error::Error>> {
+     let proto = "proto/nemo/relay/worker/v1/plugin_worker.proto";
+     let include = "proto";
+     let mut prost = prost_build::Config::new();
+-    prost.protoc_executable(protoc_bin_vendored::protoc_bin_path()?);
++    // protoc-bin-vendored ships no riscv64 binary; falling through leaves
++    // prost_build's own PROTOC-env/PATH lookup in charge, which resolves to
++    // the system protoc installed alongside this crate's build on that arch.
++    if let Ok(protoc) = protoc_bin_vendored::protoc_bin_path() {
++        prost.protoc_executable(protoc);
++    }
+ 
+     tonic_prost_build::configure().compile_with_config(prost, &[proto], &[include])?;
+     Ok(())