deploy-docs CI rejects micro-calver tags (4-part versions) #141

New issue

Closed

opened 2026-08-12 03:56:04 +00:00 by agent-pi · 1 comment

agent-pi commented

2026-08-12 03:56:04 +00:00

Collaborator

Bug

The deploy-docs job in CI fails with:

Ref 2026.8.12.2 is not a version tag; aborting.

Root cause

The regex guard in .forgejo/workflows/ci.yml line 94:

[[ $TAG_NAME =~ ^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}$ ]]

Only matches 3-part calver (e.g. 2026.8.12), but the new micro-calver scheme from issue #137 uses 4-part tags (e.g. 2026.8.12.2).

Fix

Update the regex to allow an optional 4th component:

[[ $TAG_NAME =~ ^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}(\.[0-9]+)?$ ]]

## Bug The `deploy-docs` job in CI fails with: ``` Ref 2026.8.12.2 is not a version tag; aborting. ``` ## Root cause The regex guard in `.forgejo/workflows/ci.yml` line 94: ```bash [[ $TAG_NAME =~ ^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}$ ]] ``` Only matches 3-part calver (e.g. `2026.8.12`), but the new micro-calver scheme from issue #137 uses 4-part tags (e.g. `2026.8.12.2`). ## Fix Update the regex to allow an optional 4th component: ```bash [[ $TAG_NAME =~ ^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}(\.[0-9]+)?$ ]] ```

agent-pi commented

2026-08-12 03:56:30 +00:00

Author

Collaborator

Plan

Update regex in .forgejo/workflows/ci.yml line 94 from ^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}$ to ^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}(\.[0-9]+)?$

One-line fix. Same branch as #140 (fix/issue-140-141-regressions).

**Plan** 1. Update regex in `.forgejo/workflows/ci.yml` line 94 from `^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}$` to `^[0-9]{4}\.[0-9]{1,2}\.[0-9]{1,2}(\.[0-9]+)?$` One-line fix. Same branch as #140 (`fix/issue-140-141-regressions`).

agent-pi referenced this issue from a commit

2026-08-12 03:57:19 +00:00

:bug: Fix deploy-docs CI regex to accept 4-part micro-calver tags

agent-pi referenced this issue from a pull request that will close it,

2026-08-12 03:57:32 +00:00

Fix: startup crash on shallow Dahua layout + deploy-docs CI micro-calver regex #142