argoyleandClaude Opus 5.5
6a3177457b
Release.yml still pointed GITEA_URL at the AWS in-cluster service (gitea-http.gitea.svc.cluster.local), which does not resolve from the Frostmoln runner: every release fails creating the branch with curl exit 6 (e.g. auth0mock run 34722). Use gitea.server_url. Also drop RELEASE_TOKEN_FILE=/runner-secrets/release-token (the AWS runner mount); the Frostmoln runner exports RELEASE_TOKEN_FILE itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu
Shared Workflows
Reusable Gitea Actions workflows for Unbound Software repositories.
Available Workflows
Release.yml
Automated release workflow using git-cliff for changelog generation.
Usage:
name: Release
on:
push:
branches: [main]
jobs:
release:
uses: unboundsoftware/shared-workflows/.gitea/workflows/Release.yml@main
Inputs:
tag_only(boolean, default:false): Set totrueto only create tags without full releases
Requirements:
This workflow reads the release token from /runner-secrets/release-token, which is automatically available on Unbound's Gitea runners. No repository secrets need to be configured.
How it works:
- On each push to the default branch, generates a changelog using git-cliff
- Creates or updates a
next-releasebranch with the updated CHANGELOG.md and .version file - Opens or updates a PR titled "chore(release): prepare for vX.Y.Z"
- When the .version file exists (after merging the release PR), creates a Gitea release with the changelog