argoyle 581ccba72e fix: make release PR creation robust against race conditions
Two fixes:
- Use BASE_BRANCH (with fallback) instead of DEFAULT_BRANCH for the
  PR base field, preventing empty base causing 404
- Replace fixed sleep with branch readiness poll (up to 10 attempts)
  and add retry loop for PR creation (up to 5 attempts), fixing
  intermittent 404 when Gitea hasn't indexed the branch yet

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-23 16:51:47 +01:00

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 to true to 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:

  1. On each push to the default branch, generates a changelog using git-cliff
  2. Creates or updates a next-release branch with the updated CHANGELOG.md and .version file
  3. Opens or updates a PR titled "chore(release): prepare for vX.Y.Z"
  4. When the .version file exists (after merging the release PR), creates a Gitea release with the changelog
S
Description
No description provided
Readme 76 KiB
Languages
Markdown 100%