Keeping ReadyStack images up to date

Every ReadyStack release tag names one image and never moves, so pulling the same tag again never changes what you run. To be offered each new release automatically, point Renovate at our preset: it opens a pull request for a new revision or a new upstream version, and leaves everything else alone.

How release tags work

A release tag is <upstream-version>-CE-<base-os>-r<N>, for example readystack/postgresql:18.6-CE-ubuntu24.04-r3.

What changed	The new tag
We rebuilt the same upstream version: a base-image update, a security fix, a packaging fix	The next revision: `18.6-CE-ubuntu24.04-r4`
A new upstream release	Its version, revision 1: `18.7-CE-ubuntu24.04-r1`
A move to another base OS	Another `<base-os>`: the release notes say so, and you change the tag by hand once

Tags that begin with internal- are build-pipeline artifacts: never pull them. Earlier release tags stay pullable but are no longer re-graded; every release's notes name the release they supersede.

Renovate

Wherever Renovate reads image tags: Compose files, Dockerfiles, Helm values

Add our preset to your repository's renovate.json:

{
  "extends": ["config:recommended", "https://readystack.dev/renovate/readystack.json"]
}

For every readystack/<product> image, the preset reads the upstream version as the version number and the revision after it, so Renovate:

offers the next revision of the version you run (r3 to r4), and a new upstream release (18.6 to 18.7; a new major version as its own pull request, as Renovate does for any image);
compares the numbers as numbers (8.10.10 is newer than 8.10.2);
never offers an internal- tag, and never another base OS (-CE-ubuntu24.04 stays -CE-ubuntu24.04).

Products whose upstream versions are not plain numbers have their own rules in the preset: Canvas LMS (dated releases), Jitsi Meet (stable-<n>), PostHog (builds of its main branch), MinIO (RELEASE.<date>) and Wiki.js (its beta builds). The preset is a plain JSON file: copy it into your repository instead of extending the URL if you prefer to pin it.

Checked 2026-10-27 with Renovate 42 and 44: the preset passes renovate-config-validator, every release tag on sale parses under it, and a lookup run on a sample Compose file offered postgresql 18.6-CE-ubuntu24.04-r2 to r3 and woodpecker v3.19.0-CE-ubuntu24.04-r1 to r2.

Other update tools

Any tool that filters tags with a regular expression and sorts on its captured numbers can follow our tags. For the products with plain version numbers:

^v?(?<major>\d+)\.(?<minor>\d+)(?:\.(?<patch>\d+))?-CE-(?<compatibility>.+)-r(?<build>\d+)$

Sort on the upstream version first and the revision second, and keep compatibility (the base OS) equal to the one you run. Tools that only follow a moving tag such as latest cannot be used: we publish no moving tags.

Before you merge an update

Read the release notes on the release's page: they say what changed and the release it supersedes, and a revision's notes say whether it replaces that release on the same volumes. Back up first when an update moves to a new upstream version: most products migrate their data the first time the new version starts, and do not migrate it back.

See what is on sale now. Every product's current release tag, grade and release notes.Build queue Products