[BUG] Restore readable branch manual publication tags #24

Closed
opened 2026-10-20 15:56:44 +02:00 by erikinkinen · 1 comment
Owner

Summary

Branch manual builds switched from readable CI tags to Base64 names, changing their published URLs and leaving the established branch release behind.

Reproduction

Select repository erix/docs, ref type branch, and ref name feature/posix-compat at revision 505c870e2a5e900068cad24041389a8effb86395. The policy selects ci/ZmVhdHVyZS9wb3NpeC1jb21wYXQ.

Expected and actual behavior

Expected: use ci-feature-posix-compat, preserving the established ci-<sanitized-branch> convention shared with Integration. Keep nightly for main and the original name for immutable tags.

Actual: Docs selects a Base64 name; Integration retains the readable form.

Environment and identity

  • Docs: 505c870e2a5e900068cad24041389a8effb86395.
  • Integration: f7154703cbc7fd40d34beb0c4d8b92e40b18c56f.
  • Boundary: explicit branch-ref routing in the manual publisher; no guest runtime is involved.
  • Introduced in Docs 14e36d1819cdd2b78cc7698af4b75e7330e37b7d; the previous publisher used readable names.

Evidence and prior checks

The routing implementation selects the encoded name. Both the historical readable release and the current encoded release exist. A maintained-source audit finds only Docs and Integration publish branch artifacts; Integration already follows the expected convention.

Tracking

Repair in Docs PR #4.

  • Restore readable branch routing and preserve nightly/immutable-tag behavior.
  • Update documentation and route controls, including Integration's maintained routing check.
  • Restore current publication to the readable branch release with explicit repository/ref metadata.
## Summary Branch manual builds switched from readable CI tags to Base64 names, changing their published URLs and leaving the established branch release behind. ## Reproduction Select repository `erix/docs`, ref type `branch`, and ref name `feature/posix-compat` at revision `505c870e2a5e900068cad24041389a8effb86395`. The policy selects `ci/ZmVhdHVyZS9wb3NpeC1jb21wYXQ`. ## Expected and actual behavior Expected: use `ci-feature-posix-compat`, preserving the established `ci-<sanitized-branch>` convention shared with Integration. Keep `nightly` for main and the original name for immutable tags. Actual: Docs selects a Base64 name; Integration retains the readable form. ## Environment and identity - Docs: `505c870e2a5e900068cad24041389a8effb86395`. - Integration: `f7154703cbc7fd40d34beb0c4d8b92e40b18c56f`. - Boundary: explicit branch-ref routing in the manual publisher; no guest runtime is involved. - Introduced in Docs `14e36d1819cdd2b78cc7698af4b75e7330e37b7d`; the previous publisher used readable names. ## Evidence and prior checks The [routing implementation](https://git.erikinkinen.fi/erix/docs/src/commit/505c870e2a5e900068cad24041389a8effb86395/scripts/manual_publication_policy.py) selects the encoded name. Both the historical readable release and the current encoded release exist. A maintained-source audit finds only Docs and Integration publish branch artifacts; Integration already follows the expected convention. ## Tracking Repair in [Docs PR #4](https://git.erikinkinen.fi/erix/docs/pulls/4). - [x] Restore readable branch routing and preserve nightly/immutable-tag behavior. - [x] Update documentation and route controls, including Integration's maintained routing check. - [x] Restore current publication to the readable branch release with explicit repository/ref metadata.
Author
Owner

Fixed in 2e9e77c. CI 1707 passed and published the current manual at ci-feature-posix-compat. The release and tag both identify the fix. Integration already uses the same readable convention, and its routing control passes.

Fixed in [2e9e77c](https://git.erikinkinen.fi/erix/docs/commit/2e9e77cf33d08f09c03bd50453254da4ebd36278). [CI 1707](https://git.erikinkinen.fi/erix/docs/actions/runs/1707) passed and published the current manual at [ci-feature-posix-compat](https://git.erikinkinen.fi/erix/docs/releases/tag/ci-feature-posix-compat). The release and tag both identify the fix. Integration already uses the same readable convention, and its routing control passes.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:41 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/docs#24
No description provided.