All checks were successful
The 26.2-alpha release workflow hung for 15+ minutes on "apt-get install -y jq" — the runner's apt mirror was unreachable (or very slow), and the whole publish stalled. jq was only used for two tiny things: building the release-create POST body and reading the release id from the response. Both are one-liners in Python, which is guaranteed-present on the Forgejo Actions ubuntu-latest runner image. Replaced both uses; removed the apt-get step from release.yml entirely. Slow mirrors no longer block tagged releases. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
28 lines
892 B
YAML
28 lines
892 B
YAML
name: Release
|
|
|
|
# Tag-triggered: when `git push origin <version>` lands, this builds the
|
|
# release tarball and publishes it + the sha256 + release.json to the
|
|
# Forgejo releases page for that tag. Boxes then POST /api/furtka/update
|
|
# to pull from here.
|
|
#
|
|
# Version tags only (pattern matches CalVer like 26.0-alpha, 26.1, 27.0-beta).
|
|
# Documentation / random tags are ignored by the [0-9]* prefix.
|
|
on:
|
|
push:
|
|
tags: ['[0-9]*']
|
|
|
|
jobs:
|
|
release:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
fetch-depth: 0 # changelog section extraction needs history
|
|
|
|
- name: Build release tarball
|
|
run: ./scripts/build-release-tarball.sh "${GITHUB_REF_NAME}"
|
|
|
|
- name: Publish to Forgejo releases
|
|
env:
|
|
FORGEJO_TOKEN: ${{ secrets.FORGEJO_RELEASE_TOKEN }}
|
|
run: ./scripts/publish-release.sh "${GITHUB_REF_NAME}"
|