Skip to content

v1.4.3

Latest
Latest

Choose a tag to compare

View all tags
@heyvaldemar heyvaldemar released this 19 Sep 16:14
· 6 commits to main since this release
v1.4.3
89b8a53

Changed

  • itzg/mc-proxy:2026.9.1 moved to itzg/mc-proxy:2026.9.2. 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.1 -> 2026.9.2

Verdict: SAFE TO APPLY — the notes only bump the internal mc-image-helper dependency, no config, port, or volume changes named.

Breaking changes

  • none found in the notes

Variables

  • none

Data and dependencies

  • none. The only listed change is: "Update dependency itzg/mc-image-helper to v1.69.0" and "...to v1.69.1" — both internal helper-tool bumps inside the image, not a companion service (database/cache/search engine) that would need a separate pin.

Before applying

  • Update the digest/tag pin in the compose file's x-images block (itzg/mc-proxy:2026.9.1@sha256:... → 2026.9.2@sha256:...), since that is the single source of truth for the version actually deployed.
  • No data migration, no env changes, no manual steps beyond the routine pull/restart.

Notes read

  • 2026.9.2 (2026-09-18) — the only release notes provided, covering the full 2026.9.1...2026.9.2 range via the linked compare. No UPGRADING/BREAKING_CHANGES/CHANGELOG section was included for this range.
Assets 5
Loading