Skip to main content

Release notes

What changed in each Fadebox release, newest first, one page per release line:

  • Fadebox 1.5 — 1.5.0 (2026-10-14). The current line.
  • Fadebox 1.4 — 1.4.0 (2026-09-27) to 1.4.5 (2026-10-07).
  • Fadebox 1.3 — 1.3.0 (2026-09-14) to 1.3.3 (2026-09-17).
  • Fadebox 1.2 — 1.2.0 (2026-09-11) to 1.2.1 (2026-09-12).
  • Fadebox 1.1 — 1.1.0 (2026-09-05) to 1.1.5 (2026-09-10).
  • Fadebox 1.0 — 1.0.0 (2026-08-29) to 1.0.4 (2026-09-03).

Every section ends with its upgrade notes: what a release needs beyond the image change, or the word none. The procedure itself — what to check first, how to pull, what an upgrade leaves alone — is the Upgrading guide.

What a release is​

A release is the server image and the fadebox CLI, built from one tag:

  • The server image is fadebox/fadebox on Docker Hub, public, no login to pull. Each release carries three tags: its exact version (1.0.2); its line, 1.0, which follows the newest patch of that minor and never moves to the next minor; and latest, the newest release of any line. The installation compose file pins the line, so docker compose pull takes patches and leaves minors to you.
  • The CLI, fadebox-linux-amd64, ships beside it — see Install. fadebox --version names the release it came from.

Version numbers​

X.Y.Z. A minor (1.2.0) brings features and gets its own version in the docs' picker; a patch (1.0.2) brings fixes to a released minor and is documented under that minor's docs, so the 1.0 docs describe every 1.0.x release. The page for a line holds all of its releases.

The docs of an older line stay published — an installation still on it still has its documentation — and the version picker marks them as no longer maintained once the line stops receiving fixes. 1.0 to 1.3 are archived in that sense; 1.4 is not. Release notes are not versioned at all, so every line's page stays here whatever its docs are marked.