[eksrha]

Cause

The first run of the component-based Release workflow (run 20, commit e1d179d) failed in two jobs. Both are workflow wiring problems, not relctl bugs.

1. router-build: deploy/Containerfile.router does COPY /build/bin/inference-router, but the job never built the binary. The old workflow had a make build/router step before the image build; it was lost in the rewrite. Error: "/build/bin/inference-router": not found.
2. reranker-model-publish: this standalone job runs relctl release publish without actions/checkout, so relctl finds no .relctl.yaml and fails with unknown component "reranker-model": the config file defines no components. All other publish steps run inside build jobs that already check out the repository.

The chart jobs were skipped as a consequence of the router failure.

Fix

• router-build: add a Build router binary step (make build/router) before the image build.
• reranker-model-publish: add actions/checkout@v7 before the publish step.

yamllint reports only line-length warnings (pre-existing style).

State left by run 20

Component	Release	Tag	Images pushed
tei	published	tei/202611.3.1	tei-base, tei-runtime :202611.3.1
embedding-model	published	embedding-model/202611.3.1	tei-model-init bge-m3-202611.3.1
whisper	published	whisper/202611.3.1	whisper image
router	draft	none	none (build failed)
reranker-model	draft	none	both model images pushed and signed, release not published
chart	not created	none	none

How to re-run

1. Delete the two draft releases router/202611.3.1 and reranker-model/202611.3.1 (they have no git tags yet). Keep the three published releases and their tags.
2. After merging this PR, run the Release workflow manually (workflow_dispatch) with components = router,reranker-model. Do not use all: tei, embedding-model and whisper are already released.
3. The chart is released automatically after a successful router build and pins the router and tei versions. The reranker images are rebuilt and overwrite the same tags, which is harmless.
4. Note that the CalVer counter is per day: a re-run on the same day yields 202611.3.2 for the new drafts.

[github-actions]

Possible relctl commands for this Pull Request

Version scheme: calver. The version of the release is the date of the release (YYYYMM.D.N, N counts the releases of that day). Branch prefixes and comment commands have no effect.

Need more help?

Have a look at my repo

This message was created by relctl and can be disabled by the env variable RELCTL_SILENT=true