fixing release pipeline (#40)
Generate and publish developer Wiki / validate-wiki (push) Successful in 21s
Build and publish release / metadata (push) Successful in 45s
Generate and publish developer Wiki / publish-wiki (push) Successful in 12s
Build and publish release / create-release (push) Successful in 55s
Build and publish release / build (push) Failing after 23m29s
Build and publish release / publish-release (push) Skipped

Reviewed-on: #40
Co-authored-by: Koda YeenBean <n122330@gmail.com>
This commit was merged in pull request #40.
This commit is contained in:
2026-07-20 00:03:28 +01:00
committed by Koda
parent 21dda2e618
commit 308803053c
2 changed files with 15 additions and 6 deletions
+5
View File
@@ -114,6 +114,11 @@ behavior that still needs manual testing.
- Ordinary read-only commands may fail with the same `bwrap` namespace error.
When the command is safe and required, rerun it using the environment's normal
escalation/approval mechanism instead of investigating the namespace setup.
- OpenWrt's release SDK host tools and preload libraries are x86-64. When using
them through QEMU on an ARM runner, never export the SDK's fakeroot library as
host `LD_PRELOAD`; carry it in a private variable and pass it to the bundled
x86 loader with `--preload`. Validate changes with an emulated build through
mbedTLS packaging, where a broken handoff appears as a `library/...` dependency.
Agents must preserve useful environment knowledge for later agents. When a new
pitfall or workaround is verified to be deterministic or repeatedly encountered,