feat(woodpecker): upgrade to v3.16.0 + enable 3.x image automation #359

2026-07-22T14:24:49Z

claude-bot commented

2026-07-22 14:24:49 +00:00

Bumps woodpecker server + agent 3.13.0 → 3.16.0 and adds Flux image automation — now safe to do since woodpecker moved off sqlite onto CNPG postgres (#355/#356/#357).

Upgrade (reviewed, per the changelog)

No breaking changes for our kubernetes-backend + Gitea + postgres setup across 3.14/3.15/3.16; none of our WOODPECKER_* vars renamed/removed. Direct 3.13→3.16 is supported (migrations are cumulative, auto-run on startup).
Server + agent bumped together (gRPC version parity is required).
Pre-upgrade CNPG base backup taken (wp-pg-preupgrade-316, completed) — migrations are forward-only, so this is the rollback path.

Image automation (answers "why is there no image automation on this?")

It was deliberately excluded while on sqlite — a surprise bump across a live, never-cleanly-shut-down sqlite DB was a real hazard. That's gone on postgres. New image-automation/woodpecker.yaml:

Range 3.x — auto-take minor + patch within 3.x (matches the repo's tika convention); only the 4.0 major stays a reviewed bump (breaking changes + forward-only migrations).
Server + agent share the same range/tag-filter and both carry $imagepolicy markers → they bump in lockstep.

On merge

Flux applies → woodpecker restarts on 3.16.0, runs its migrations on postgres → agent reconnects at matching version. I'll verify health + a test pipeline, and confirm the agent shows no gRPC version-mismatch.

🤖 Generated with Claude Code

Bumps woodpecker server + agent **3.13.0 → 3.16.0** and adds Flux image automation — now safe to do since woodpecker moved off sqlite onto CNPG postgres (#355/#356/#357). ## Upgrade (reviewed, per the changelog) - **No breaking changes** for our kubernetes-backend + Gitea + postgres setup across 3.14/3.15/3.16; none of our `WOODPECKER_*` vars renamed/removed. Direct 3.13→3.16 is supported (migrations are cumulative, auto-run on startup). - Server + agent bumped **together** (gRPC version parity is required). - **Pre-upgrade CNPG base backup taken** (`wp-pg-preupgrade-316`, completed) — migrations are forward-only, so this is the rollback path. ## Image automation (answers "why is there no image automation on this?") It was deliberately excluded while on sqlite — a surprise bump across a live, never-cleanly-shut-down sqlite DB was a real hazard. **That's gone on postgres.** New `image-automation/woodpecker.yaml`: - Range **`3.x`** — auto-take minor + patch within 3.x (matches the repo's `tika` convention); only the **4.0 major** stays a reviewed bump (breaking changes + forward-only migrations). - Server + agent share the same range/tag-filter and both carry `$imagepolicy` markers → they bump **in lockstep**. ## On merge Flux applies → woodpecker restarts on 3.16.0, runs its migrations on postgres → agent reconnects at matching version. I'll verify health + a test pipeline, and confirm the agent shows no gRPC version-mismatch. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit 2026-07-22 14:24:49 +00:00

feat(woodpecker): upgrade to v3.16.0 + enable 3.x image automation 511904ae9e

Now that woodpecker runs on postgres (not the previously-pinned sqlite), the
"never surprise-bump a live sqlite DB" hazard is gone. Bump server + agent
3.13.0 -> 3.16.0 (a reviewed minor jump: no breaking config changes for our
kubernetes+gitea+postgres setup, no risky migrations per the changelog; direct
3.13->3.16 is supported, migrations run on startup).

Add Flux image automation (image-automation/woodpecker.yaml) at range 3.x, so
minor + patch releases auto-update; only the 4.0 major stays a reviewed bump.
Server and agent share the same range/tag-filter and both carry an $imagepolicy
marker, so they bump in lockstep (gRPC version parity is required).

Pre-upgrade CNPG base backup taken (wp-pg-preupgrade-316) as the rollback path,
since migrations are forward-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

k.renner merged commit ed567f300a into master

2026-07-22 14:38:15 +00:00

k.renner referenced this issue from a commit

2026-07-22 14:38:15 +00:00

Merge pull request 'feat(woodpecker): upgrade to v3.16.0 + enable 3.x image automation' (#359) from claude-bot/woodpecker-316-imgauto into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#359