Timothy reversed the 2026-07-07 version-pin decision: prod's media-servers compose now follows the floating :prod tag, redeployed by Komodo Global Auto Update (poll_for_updates is on).
So the bump-prod-compose job added in #275 — which rewrites a :<version> pin — is now wrong: it would flip :prod → :26.8.0 on the next release, silently undoing the decision. This removes it.
Changes
Remove the bump-prod-compose job from .gitea/workflows/docker-build.yml (jobs back to test/migrations/build/docs-reminder).
docs/ci-cd.md: release procedure + tag table reconciled to :prod-following (Global Auto Update deploys; immutable :<version> tags kept for reproducible rollback).
⚠️ Open caveat (flagged in the docs)
Confirm Komodo Global Auto Update runs the #553 host-side pre-deploy backup hook. If it doesn't, a release would deploy without a backup — the fallback is a manual execute DeployStack media-servers (which does run pre-deploy). This is a Komodo-side verification (server-management).
State (already live, not part of this PR)
Prod is running :prod = v26.7.0 (the #91b Blazor removal), healthy — deployed 2026-07-11.
The SERVERMGMT_DEPLOY_KEY secret + ersatztv-ci-deploy deploy key are now unused by CI (harmless to leave; remove later if desired).
Timothy reversed the 2026-07-07 version-pin decision: **prod's `media-servers` compose now follows the floating `:prod` tag**, redeployed by **Komodo Global Auto Update** (`poll_for_updates` is on).
So the `bump-prod-compose` job added in #275 — which rewrites a `:<version>` pin — is now **wrong**: it would flip `:prod` → `:26.8.0` on the next release, silently undoing the decision. This removes it.
## Changes
- Remove the `bump-prod-compose` job from `.gitea/workflows/docker-build.yml` (jobs back to test/migrations/build/docs-reminder).
- `docs/ci-cd.md`: release procedure + tag table reconciled to `:prod`-following (Global Auto Update deploys; immutable `:<version>` tags kept for reproducible rollback).
## ⚠️ Open caveat (flagged in the docs)
Confirm **Komodo Global Auto Update runs the #553 host-side pre-deploy backup** hook. If it doesn't, a release would deploy without a backup — the fallback is a manual `execute DeployStack media-servers` (which does run pre-deploy). This is a Komodo-side verification (server-management).
## State (already live, not part of this PR)
- Prod is running `:prod` = **v26.7.0** (the #91b Blazor removal), healthy — deployed 2026-07-11.
- The `SERVERMGMT_DEPLOY_KEY` secret + `ersatztv-ci-deploy` deploy key are now unused by CI (harmless to leave; remove later if desired).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Timothy reversed the version-pin decision: prod's media-servers compose now
follows the floating :prod tag, redeployed by Komodo Global Auto Update. The
bump-prod-compose job (#275) rewrote a :<version> pin, which would flip :prod ->
:26.8.0 on the next release — remove it. docs/ci-cd.md reconciled to the :prod
model (+ flags the open caveat: verify Global Auto Update runs the #553
pre-deploy backup, else releases deploy without a backup).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timothy
merged commit 1b5efd7b9d into main2026-07-11 22:31:15 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Timothy reversed the 2026-07-07 version-pin decision: prod's
media-serverscompose now follows the floating:prodtag, redeployed by Komodo Global Auto Update (poll_for_updatesis on).So the
bump-prod-composejob added in #275 — which rewrites a:<version>pin — is now wrong: it would flip:prod→:26.8.0on the next release, silently undoing the decision. This removes it.Changes
bump-prod-composejob from.gitea/workflows/docker-build.yml(jobs back to test/migrations/build/docs-reminder).docs/ci-cd.md: release procedure + tag table reconciled to:prod-following (Global Auto Update deploys; immutable:<version>tags kept for reproducible rollback).⚠️ Open caveat (flagged in the docs)
Confirm Komodo Global Auto Update runs the #553 host-side pre-deploy backup hook. If it doesn't, a release would deploy without a backup — the fallback is a manual
execute DeployStack media-servers(which does run pre-deploy). This is a Komodo-side verification (server-management).State (already live, not part of this PR)
:prod= v26.7.0 (the #91b Blazor removal), healthy — deployed 2026-07-11.SERVERMGMT_DEPLOY_KEYsecret +ersatztv-ci-deploydeploy key are now unused by CI (harmless to leave; remove later if desired).🤖 Generated with Claude Code