enricobuehlerandClaude Opus 4.8
15d09a8c10
ci / web (push) Successful in 51s
ci / docs-site (push) Successful in 1m5s
apple / swift (push) Successful in 1m25s
decky / build-publish (push) Successful in 21s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 9s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 10s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 9s
docker / build-push (ci, ci/rust-ci-noble.Dockerfile, punktfunk-rust-ci-noble) (push) Successful in 9s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 10s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 10s
ci / bench (push) Successful in 6m55s
apple / screenshots (push) Successful in 6m47s
deb / build-publish (push) Successful in 11m23s
android / android (push) Successful in 12m36s
arch / build-publish (push) Successful in 12m46s
docker / deploy-docs (push) Successful in 23s
deb / build-publish-host (push) Successful in 12m32s
rpm / build-publish (43, bazzite, punktfunk-fedora-rpm) (push) Successful in 16m9s
ci / rust (push) Successful in 26m29s
rpm / build-publish (44, fedora-44, punktfunk-fedora44-rpm) (push) Successful in 20m30s
Release notes now live in the repo at docs/releases/vX.Y.Z.md, authored during the version bump (before the tag). ensure_release (gitea-release.sh + .ps1 twin) seeds the Gitea release body from that file in the create POST, so the release is born WITH its notes instead of being created empty and PATCHed afterward. canary/rc have no file -> empty body, unchanged. New manual `announce` workflow (workflow_dispatch, tag input) re-syncs the notes file over the live release and posts a violet embed (title, notes lead-in, release-page link) to the Discord #releases channel via the DISCORD_RELEASE_WEBHOOK secret. Stable-only: a -rc tag is refused unless allow_prerelease=true. Pressing "go" is the quality gate, so a half-built or failed release is never announced. docs/releases/README.md documents the ritual; TEMPLATE.md is the skeleton. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
40 lines
1.6 KiB
YAML
40 lines
1.6 KiB
YAML
# Announce a stable release to the Discord #releases channel.
|
|
#
|
|
# This is the deliberate "go" step for a release. Release notes live in the repo at
|
|
# docs/releases/<tag>.md and are seeded into the Gitea release body at creation by the build
|
|
# workflows (scripts/ci/gitea-release.sh), so the release is never noteless. Once every
|
|
# platform's CI is green for a tag, dispatch this workflow with that tag: it re-asserts the notes
|
|
# file over the live release and posts a formatted embed to #releases.
|
|
#
|
|
# Manual on purpose — pressing "go" is the quality gate that says "all platforms built, notes are
|
|
# final, tell the community." It is NOT wired to the tag push, so a half-built or failed release
|
|
# is never announced. Stable-only: a -rc/pre-release tag is refused unless allow_prerelease=true.
|
|
#
|
|
# Requires the repo secret DISCORD_RELEASE_WEBHOOK (the #releases channel webhook URL); GITEA auth
|
|
# reuses REGISTRY_TOKEN like the other release workflows.
|
|
name: announce
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
inputs:
|
|
tag:
|
|
description: "Release tag to announce (e.g. v0.18.0)"
|
|
required: true
|
|
allow_prerelease:
|
|
description: "Announce even if the tag is a pre-release (-rc)"
|
|
required: false
|
|
default: "false"
|
|
|
|
jobs:
|
|
announce:
|
|
runs-on: ubuntu-24.04
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: Post release announcement to Discord
|
|
env:
|
|
GITEA_TOKEN: ${{ secrets.REGISTRY_TOKEN }}
|
|
DISCORD_RELEASE_WEBHOOK: ${{ secrets.DISCORD_RELEASE_WEBHOOK }}
|
|
ALLOW_PRERELEASE: ${{ inputs.allow_prerelease }}
|
|
run: bash scripts/ci/discord-announce.sh "${{ inputs.tag }}"
|