fix(ci): correct MAJOR tag derivation #7

Merged

w33ble merged 1 commit from fix/release-major-tag into main

2026-09-06 13:59:33 -06:00

hijynx commented

2026-09-06 13:54:27 -06:00

Collaborator

Problem

The v1.1.x release runs pushed a git.w33ble.com/w33ble/lagom:vv1 image tag instead of :v1.

Cause (.forgejo/workflows/release.yaml:19):

MAJOR="v${TAG#v}" ; MAJOR="v${MAJOR%%.*}"

MAJOR is assigned twice: the first assignment re-prepends v (v1.2.0), then the second prepends v again before trimming the minor/patch part → vv1.

Fix

Single line, no double prefix:

MAJOR="${TAG%%.*}"   # v1.2.0 -> v1

Verified against v1.2.0 → v1, v1.0.0-rc1 → v1, v10.5.3 → v10.

Registry cleanup needed

The bad vv1 image tag already exists in the registry from the previous release run and should be deleted manually (Forgejo package UI or API).

## Problem The v1.1.x release runs pushed a `git.w33ble.com/w33ble/lagom:vv1` image tag instead of `:v1`. **Cause** (`.forgejo/workflows/release.yaml:19`): ```sh MAJOR="v${TAG#v}" ; MAJOR="v${MAJOR%%.*}" ``` `MAJOR` is assigned twice: the first assignment re-prepends `v` (`v1.2.0`), then the second prepends `v` again before trimming the minor/patch part → `vv1`. ## Fix Single line, no double prefix: ```sh MAJOR="${TAG%%.*}" # v1.2.0 -> v1 ``` Verified against `v1.2.0` → `v1`, `v1.0.0-rc1` → `v1`, `v10.5.3` → `v10`. ## Registry cleanup needed The bad `vv1` image tag already exists in the registry from the previous release run and should be deleted manually (Forgejo package UI or API).

hijynx added 1 commit

2026-09-06 13:54:27 -06:00