ci: use semver-baseline tag pattern (1.0.0-baseline)

This commit is contained in:
germondai
2026-06-30 23:30:48 +02:00
parent 0a32a05cff
commit f9a3a0314c
2 changed files with 7 additions and 6 deletions
+6 -5
View File
@@ -3,13 +3,13 @@ name: Publish Baseline
# Builds the `:baseline` tag of `ghcr.io/.../trawl` from
# `apps/api/Dockerfile.baseline` (Bun baseline runtime — pre-2013-CPU
# compatible). Same GHCR package as `:latest`, just a different tag.
# Triggered manually, or automatically on `baseline-v*` tags which stamp
# `:baseline-vX.Y.Z`.
# Triggered manually, or automatically on `*-baseline` tags (e.g. `1.0.0-baseline`),
# which produce the docker tag `germondai/trawl:1.0.0-baseline`.
on:
workflow_dispatch:
push:
tags: ["baseline-v*"]
tags: ["*-baseline"]
env:
IMAGE: ghcr.io/${{ github.repository_owner }}/trawl
@@ -43,8 +43,9 @@ jobs:
shell: bash
run: |
if [[ "${{ github.event_name }}" == "push" ]]; then
VER="${GITHUB_REF_NAME#baseline-v}"
TAGS="${IMAGE}:baseline-v${VER}"
# Tag push: docker tag mirrors git tag exactly.
# Pattern: git tag `1.0.0-baseline` → `germondai/trawl:1.0.0-baseline`
TAGS="${IMAGE}:${GITHUB_REF_NAME}"
else
# Manual dispatch: only update :baseline if on default branch
if [[ "${{ github.ref }}" == "refs/heads/main" ]]; then
+1 -1
View File
@@ -111,7 +111,7 @@ image: ghcr.io/germondai/trawl:latest
image: ghcr.io/germondai/trawl:baseline
```
Synology note: many Synology NAS units (DSM 7.x on J4125 / older hardware) ship kernel 4.4.x, which Bun's modern runtime can't fully handle. The `:baseline` tag is published for that case — confirm-working status on the reporter's actual hardware (DS920+, kernel 4.4.302) is pending verification. Published by independent GitHub Actions workflows (`.github/workflows/publish.yml`, `publish-baseline.yml`); tag-triggered releases (`v*`, `baseline-v*`) and manual `workflow_dispatch` both work.
Synology note: many Synology NAS units (DSM 7.x on J4125 / older hardware) ship kernel 4.4.x, which Bun's modern runtime can't fully handle. The `:baseline` tag is published for that case — confirm-working status on the reporter's actual hardware (DS920+, kernel 4.4.302) is pending verification. Published by independent GitHub Actions workflows (`.github/workflows/publish.yml`, `publish-baseline.yml`); tag-triggered releases push matching git tags (e.g. `v1.0.0``1.0.0`, `1.0.0-baseline``1.0.0-baseline`) and manual `workflow_dispatch` from `main` updates the rolling tag (`latest` and `baseline` respectively).
## Configuration