v1.4.2

Changed

• itzg/mc-proxy:2026.9.0 moved to itzg/mc-proxy:2026.9.1. The freshness check reported the lag; the deploy job booted the stack on the new image before this landed.

Upgrading

git pull (or ./update.sh), then docker compose up -d. Containers on a refreshed image are recreated; data volumes and .env are untouched. This release was cut by fleet triage after the deploy job booted the stack on the refreshed images.

Full history in CHANGELOG.md.

What upstream changed

Read by fleet triage from the upstream release notes (or the commits between the tags) against this compose file, before the bump was applied.

Upstream changes 2026.9.0 -> 2026.9.1

Verdict: SAFE TO APPLY — the notes contain only internal dependency bumps (mc-image-helper, a build-time GitHub Action), no breaking changes, no variable changes, and no companion-service version is named.

Breaking changes

• none found in the notes

Variables

• none

Data and dependencies

• none. The only version references are Update dependency itzg/mc-image-helper to v1.67.2 and Update dependency itzg/mc-image-helper to v1.68.0 — an internal build helper bundled in the image, not a database/cache/search-engine companion service that would need a matching pin in the compose file.

Before applying

• None required beyond the normal git pull / redeploy flow this template is designed for. No config edit, backup, or manual migration is called for by these notes.

Notes read

• 2026.9.1 (2026-09-11), full changelog range 2026.9.0...2026.9.1 — this is the only version step in the range, so no earlier tags needed reading.