Fix deployment image tag to correct merge commit SHA #93

Merged

forgejo_admin merged 5 commits from 92-fix-deployment-image-tag into main

2026-03-07 12:33:11 +00:00

forgejo_admin commented

2026-03-06 22:24:00 +00:00

Contributor

Summary

Update k8s/deployment.yaml image tag from c85a39da313a80ebde109895fd281cd7ff7c9275 to 2eddd7660bccbd38f5cc2e53907f2f5485a74ef0, pointing to the actual merge commit on main that includes the full-text search changes.

Changes

k8s/deployment.yaml — updated container image tag to the correct merge commit SHA

Test Plan

ArgoCD detects the change and rolls the pod
New pod starts successfully with the correct image
/healthz endpoint responds
No regressions in existing functionality

Review Checklist

Passed automated review-fix loop
No secrets committed
No unnecessary file changes
Commit messages are descriptive

plan-2026-02-26-tf-modularize-postgres — Phase 5 deployment
Forgejo issue: #92

## Summary Update `k8s/deployment.yaml` image tag from `c85a39da313a80ebde109895fd281cd7ff7c9275` to `2eddd7660bccbd38f5cc2e53907f2f5485a74ef0`, pointing to the actual merge commit on main that includes the full-text search changes. ## Changes - `k8s/deployment.yaml` — updated container image tag to the correct merge commit SHA ## Test Plan - [ ] ArgoCD detects the change and rolls the pod - [ ] New pod starts successfully with the correct image - [ ] `/healthz` endpoint responds - [ ] No regressions in existing functionality ## Review Checklist - [ ] Passed automated review-fix loop - [ ] No secrets committed - [ ] No unnecessary file changes - [ ] Commit messages are descriptive ## Related Notes - `plan-2026-02-26-tf-modularize-postgres` — Phase 5 deployment - Forgejo issue: #92

forgejo_admin added 1 commit

2026-03-06 22:24:00 +00:00

Fix deployment image tag to correct merge commit SHA

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

e33f43906c

Update k8s/deployment.yaml image tag from c85a39da to 2eddd766,
pointing to the actual merge commit on main.

Closes #92

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

forgejo_admin added 1 commit

2026-03-07 12:22:55 +00:00

Switch deployment strategy from Recreate to RollingUpdate

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

672b099228

Recreate kills the old pod before the new one starts, which caused a
15-minute outage when an invalid image tag was deployed. With Postgres
(not SQLite), there's no single-writer constraint — multiple pods can
safely connect. RollingUpdate with maxUnavailable=0 ensures the old pod
keeps serving until the new one passes its readiness probe.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

forgejo_admin added 1 commit

2026-03-07 12:28:01 +00:00

Add CI step to auto-update deployment image tag after build

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

ab24f19692

After a successful build-and-push, Woodpecker now updates
k8s/deployment.yaml with the new CI_COMMIT_SHA and pushes to main.
Path exclusion prevents infinite CI loops. Eliminates manual image
tag management that caused the Phase 5 deployment outage.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

forgejo_admin added 1 commit

2026-03-07 12:29:38 +00:00

Fix CI commit-back auth: use existing forgejo_user/password globals

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

cc0aa953fb

The forgejo_token secret doesn't exist. Use the existing global
forgejo_user and forgejo_password secrets for git push auth.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

forgejo_admin added 1 commit

2026-03-07 12:31:57 +00:00

Use forgejo_token for CI commit-back auth

ci/woodpecker/pr/woodpecker Pipeline was successful

Details

cb1343ddc4

Repo secret forgejo_token now exists in Woodpecker. Simpler than
user/password pair — single token auth.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>