T

feat(release): rebase PR branch before updating changelog

When updating an existing release PR, the workflow now rebases
the next-release branch onto the base branch using Gitea's PR
update API with style=rebase. This keeps the PR up to date with
main without force-pushing or deleting the branch.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-09 21:09:21 +01:00

.claude

feat(release): rebase PR branch before updating changelog

2026-01-09 21:09:21 +01:00

.gitea/workflows

feat(release): rebase PR branch before updating changelog

2026-01-09 21:09:21 +01:00

CLAUDE.md

fix: remove containers from workflow to fix Node.js compatibility

2026-01-09 04:48:47 +01:00

README.md

feat: use file-based release token instead of secret

2026-01-08 21:48:17 +01:00

renovate.json

fix: remove containers from workflow to fix Node.js compatibility

2026-01-09 04:48:47 +01:00

README.md

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:

On each push to the default branch, generates a changelog using git-cliff
Creates or updates a next-release branch 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