furtka-apps/.forgejo/workflows/release.yml
Daniel Maksymilian Syrnicki 8cd9e3bcf4
All checks were successful
CI / validate (push) Successful in 36s
CI / shellcheck (push) Successful in 1m1s
Release / release (push) Successful in 38s
chore: bootstrap furtka-apps catalog repo
Initial layout: apps/fileshare/ (seeded from daniel/furtka apps/), CI
(JSON + manifest validator + shellcheck), release pipeline (tag-driven,
mirrors core repo), vendored manifest schema for offline validation.

The core repo (daniel/furtka) at 26.6-alpha keeps apps/fileshare as a
seed so offline first-boot still has an installable app; this catalog
becomes authoritative once a box has synced at least once.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 14:14:50 +02:00

28 lines
892 B
YAML

name: Release
# Tag-triggered: when `git push origin <version>` lands, this builds the
# catalog tarball and publishes it + the sha256 + release.json to the
# Forgejo releases page for that tag. Running Furtka boxes pull from here
# on their daily furtka-catalog-sync.timer.
#
# Version tags only (CalVer like 26.0, 26.1-alpha, 27.0-beta). 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 catalog tarball
run: ./scripts/build-catalog-tarball.sh "${GITHUB_REF_NAME}"
- name: Publish to Forgejo releases
env:
FORGEJO_TOKEN: ${{ secrets.FORGEJO_RELEASE_TOKEN }}
run: ./scripts/publish-catalog-release.sh "${GITHUB_REF_NAME}"