From 6339771a240dccf1442f94002c7c65f4236271f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Balv=C3=ADn?= Date: Sun, 26 Jul 2026 20:31:11 +0200 Subject: [PATCH] feat(ci): add riscv64 and loong64 build targets --- .gitea/workflows/release.yml | 6 ++++++ CONTRIBUTING.md | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/release.yml b/.gitea/workflows/release.yml index 3a24c05..db111f3 100644 --- a/.gitea/workflows/release.yml +++ b/.gitea/workflows/release.yml @@ -15,10 +15,16 @@ jobs: goarch: amd64 - goos: linux goarch: arm64 + - goos: linux + goarch: riscv64 + - goos: linux + goarch: loong64 - goos: freebsd goarch: amd64 - goos: freebsd goarch: arm64 + - goos: freebsd + goarch: riscv64 steps: - uses: actions/checkout@v4 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f733903..58fdf84 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -229,7 +229,7 @@ just build Triggered by pushing a tag that matches `v*.*.*` (e.g. `v1.0.0`, `v1.2.3`) onto `main`. The merge from `development` into `main` is the maintainer's responsibility and happens before the tag is pushed — this workflow does not merge anything. Two jobs: -1. **`build`** — Runs on a `fedora` runner in a 4-way matrix: `linux/amd64`, `linux/arm64`, `freebsd/amd64`, `freebsd/arm64`. The default `actions/checkout@v4` checks out the tagged commit (the trigger was a tag push), which is exactly the commit on `main` we want to ship. The version is baked in via `-ldflags`: +1. **`build`** — Runs on a `fedora` runner in a 7-way matrix: `linux/amd64`, `linux/arm64`, `linux/riscv64`, `linux/loong64`, `freebsd/amd64`, `freebsd/arm64`, `freebsd/riscv64`. The default `actions/checkout@v4` checks out the tagged commit (the trigger was a tag push), which is exactly the commit on `main` we want to ship. The version is baked in via `-ldflags`: ```bash -X sourcedock.dev/petrbalvin/nuntius/internal/version.Version=${VERSION#v} ```