fixing release pipeline again (#31)
Build and publish release / metadata (push) Successful in 34s
Build and publish release / create-release (push) Successful in 50s
Build and publish release / build (push) Failing after 4m34s
Build and publish release / publish-release (push) Skipped

Reviewed-on: #31
This commit was merged in pull request #31.
This commit is contained in:
2026-07-15 20:37:15 +01:00
parent 208b49b512
commit c406d20ac2
3 changed files with 48 additions and 1 deletions
+6
View File
@@ -61,6 +61,12 @@ Add an object with a unique `architecture` label and a valid OpenWrt
required. The generic ARM entries select ARMv7 and ARMv8 ABIs; use a
device-specific OpenWrt target when necessary.
OpenWrt publishes its release SDKs with x86-64 host tools, even when the target
is ARM or PowerPC. On an ARM build agent, the workflow installs
`qemu-user-static` and the build script runs the SDK host tools explicitly
through `qemu-x86_64-static`; privileged `binfmt_misc` registration is not
required. Native x86-64 agents skip emulation and remain faster.
Releases use the next available `MAJOR.MINOR.PATCH` tag. `MAJOR` and `MINOR`
live in the release config; the workflow finds the highest existing
`vMAJOR.MINOR.PATCH` tag and increments its patch, starting at `0` when a new