carrier/.forgejo/workflows/release.yml
randogoth 1bbc961bd6
All checks were successful
CI / macos (push) Successful in 37s
Release / macos (push) Successful in 36s
CI / linux (push) Successful in 3m43s
Release / linux (push) Successful in 2m49s
Release / release (push) Successful in 11s
Fix release workflow: use Forgejo's upload/download-artifact fork
actions/upload-artifact@v4 and download-artifact@v4 use GitHub's newer
Artifacts-v2 protocol, which Forgejo's server explicitly refuses
("not currently supported on GHES"). Forgejo maintains its own forks
(forgejo/upload-artifact@v5, forgejo/download-artifact@v7) with that
check disabled. Also drops archive: false, an input that fork doesn't
expose - the earlier binary rename already keeps filenames distinct
through the default zip/extract round-trip.
2026-10-07 20:07:09 +03:00

96 lines
3.4 KiB
YAML

name: Release
on:
push:
tags: ["v*"]
jobs:
macos:
runs-on: macos-arm64
steps:
- uses: https://code.forgejo.org/actions/checkout@v4
with:
path: carrier
- uses: https://code.forgejo.org/actions/checkout@v4
with:
repository: randogoth/fumi
ref: main
path: fumi
- uses: https://code.forgejo.org/actions/cache@v4
with:
path: |
~/.cargo/registry
carrier/target
fumi/target
key: cargo-macos-${{ hashFiles('carrier/Cargo.lock') }}
restore-keys: cargo-macos-
- run: devbox run build
working-directory: carrier
env:
GITHUB_TOKEN: ""
- run: mv target/release/carrier target/release/carrier-macos-arm64
working-directory: carrier
# actions/upload-artifact@v4 talks the newer Artifacts-v2 protocol,
# which Forgejo's server rejects ("not currently supported on GHES").
# forgejo/upload-artifact is Forgejo's own patched fork with that
# check disabled - needed on both upload and download ends.
- uses: https://code.forgejo.org/forgejo/upload-artifact@v5
with:
name: carrier-macos-arm64
path: carrier/target/release/carrier-macos-arm64
linux:
runs-on: linux-x86_64
steps:
- uses: https://code.forgejo.org/actions/checkout@v4
with:
path: carrier
- uses: https://code.forgejo.org/actions/checkout@v4
with:
repository: randogoth/fumi
ref: main
path: fumi
- uses: https://code.forgejo.org/actions/cache@v4
with:
path: |
~/.cargo/registry
carrier/target
fumi/target
key: cargo-linux-${{ hashFiles('carrier/Cargo.lock') }}
restore-keys: cargo-linux-
- run: devbox run build
working-directory: carrier
env:
GITHUB_TOKEN: ""
- run: mv target/release/carrier target/release/carrier-linux-x86_64
working-directory: carrier
- uses: https://code.forgejo.org/forgejo/upload-artifact@v5
with:
name: carrier-linux-x86_64
path: carrier/target/release/carrier-linux-x86_64
# forgejo-release.sh (the engine behind actions/forgejo-release) always
# does a blind create-then-upload of the release for the tag, with no
# check for one already existing - running it from two parallel jobs
# against the same tag either hard-fails the second create (override:
# false) or races a delete-and-recreate that can wipe out the first job's
# just-uploaded assets (override: true). So platform jobs only ever
# produce artifacts; exactly one job, gated on both finishing, does the
# single release create + upload.
release:
needs: [macos, linux]
runs-on: linux-x86_64
steps:
- uses: https://code.forgejo.org/forgejo/download-artifact@v7
with:
path: dist/release
merge-multiple: true
- uses: https://code.forgejo.org/actions/forgejo-release@v2.13.4
with:
direction: upload
release-dir: dist/release
# Safe here specifically because this is the only job that ever
# calls forgejo-release for a given tag: re-running this same job
# for the same tag (e.g. a manual rerun) replaces its release
# cleanly instead of failing on "already exists".
override: true