[PR #42] [MERGED] Fix release automation: merge auto-tag + release into single workflow #56

New issue

Closed

opened 2026-10-15 12:55:15 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 12:55:15 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/games-on-whales/unraid-plugin/pull/42
Author: @JBailes
Created: 5/25/2026
Status: ✅ Merged
Merged: 5/25/2026
Merged by: @JBailes

Base: main ← Head: fix/auto-release-workflow

📝 Commits (1)

5d5ecfe Replace split auto-tag + release workflows with a single auto-release workflow

📊 Changes

3 files changed (+100 additions, -96 deletions)

View changed files

➕ .github/workflows/auto-release.yml (+100 -0)
➖ .github/workflows/auto-tag.yml (+0 -40)
➖ .github/workflows/release.yml (+0 -56)

📄 Description

Problem

Every merge to main should produce a GitHub release, but the two-workflow chain was silently broken.

auto-tag.yml pushed a version tag using GITHUB_TOKEN. GitHub's loop-prevention policy means events triggered by GITHUB_TOKEN cannot start other workflows, so release.yml never fired after the tag was created. The 2026.05.25 tag was created successfully but no release was ever built — which is what the reporter in issue #40 is seeing.

Fix

Replace both workflows with a single auto-release.yml that does everything in one job:

Determines the next version — reads existing tags for today (YYYY.MM.DD*) and increments the suffix (a, b, …) if today already has a release. Every merge to main gets a release even if the PR didn't bump gow.plg.
Updates gow.plg — bumps the <!ENTITY version> line and commits it back to main if the version changed.
Creates the tag — skips if it already exists (safe for manual re-runs).
Builds settings-ui.txz and publishes the GitHub release with auto-generated release notes.

workflow_dispatch is included with an optional version input so we can immediately fix the missing 2026.05.25 release by re-running for that tag.

Immediate follow-up after merge

Trigger the workflow manually at Actions → auto-release → Run workflow with version = 2026.05.25 to publish the missing release for the appdata fix.

Test plan

Merge this PR → confirm auto-release run creates tag and release for today
Merge a second PR same day → confirm suffix (a) is appended correctly
Run workflow manually with version = 2026.05.25 → confirm missing release is published

Closes #40

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/games-on-whales/unraid-plugin/pull/42 **Author:** [@JBailes](https://github.com/JBailes) **Created:** 5/25/2026 **Status:** ✅ Merged **Merged:** 5/25/2026 **Merged by:** [@JBailes](https://github.com/JBailes) **Base:** `main` ← **Head:** `fix/auto-release-workflow` --- ### 📝 Commits (1) - [`5d5ecfe`](https://github.com/games-on-whales/unraid-plugin/commit/5d5ecfe379a7ba338769873450517b43ab92bf7a) Replace split auto-tag + release workflows with a single auto-release workflow ### 📊 Changes **3 files changed** (+100 additions, -96 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/auto-release.yml` (+100 -0) ➖ `.github/workflows/auto-tag.yml` (+0 -40) ➖ `.github/workflows/release.yml` (+0 -56) </details> ### 📄 Description ## Problem Every merge to main should produce a GitHub release, but the two-workflow chain was silently broken. `auto-tag.yml` pushed a version tag using `GITHUB_TOKEN`. GitHub's loop-prevention policy means **events triggered by `GITHUB_TOKEN` cannot start other workflows**, so `release.yml` never fired after the tag was created. The `2026.05.25` tag was created successfully but no release was ever built — which is what the reporter in issue #40 is seeing. ## Fix Replace both workflows with a single `auto-release.yml` that does everything in one job: 1. **Determines the next version** — reads existing tags for today (`YYYY.MM.DD*`) and increments the suffix (`a`, `b`, …) if today already has a release. Every merge to main gets a release even if the PR didn't bump `gow.plg`. 2. **Updates `gow.plg`** — bumps the `<!ENTITY version>` line and commits it back to main if the version changed. 3. **Creates the tag** — skips if it already exists (safe for manual re-runs). 4. **Builds `settings-ui.txz`** and **publishes the GitHub release** with auto-generated release notes. `workflow_dispatch` is included with an optional `version` input so we can immediately fix the missing `2026.05.25` release by re-running for that tag. ## Immediate follow-up after merge Trigger the workflow manually at **Actions → auto-release → Run workflow** with `version = 2026.05.25` to publish the missing release for the appdata fix. ## Test plan - [x] Merge this PR → confirm `auto-release` run creates tag and release for today - [x] Merge a second PR same day → confirm suffix (`a`) is appended correctly - [x] Run workflow manually with `version = 2026.05.25` → confirm missing release is published Closes #40 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 12:55:15 +00:00