maintenant 1.13.0 ranks image updates by how urgent they are instead of by the size of the version jump, follows the end of support of six official images, reports the update inside the current major version before the next major one, and no longer reports a stopped container as unhealthy. The severity of update alerts and the meaning of risk_score change: read Before you upgrade first.
Before you upgrade
- Update alerts. A new major version no longer raises a critical
update_availablealert by itself. On a release line that is still supported it raises an info alert. An alert trigger or an escalation policy filtered on thecriticalseverity now fires for other updates: those whose running version is out of support and, with CVE enrichment, those that fix a critical vulnerability. - Alerts raised before the upgrade. The upgrade sets the open critical
update_availablealerts to info, silenced ones included. The first scan raises again the ones that are critical under the new rules, with a "Severity raised" notification. maintenant.update.alert_on: critical. The label keeps the updates with a risk score of 81 or more, no longer the major ones.- Release lines out of support. An update of an official
postgres,mysql,mariadb,redis,mongoornginximage becomes Critical, with a critical alert, when the release line that runs is out of support. At the date of this release that covers PostgreSQL 14 and MySQL 8.0, among others. risk_score. The value measures urgency: a major update scores 20 instead of 85, a patch 45 instead of 15. A client that readsrisk_scorefrom the API, MCP or theupdate.detectedevent to pick out major updates must readupdate_typeinstead.- Version reported. When a newer version exists inside the current major version, it replaces the later major version that was reported until now. The alert of such a container is resolved and raised again once, at the first scan, with the new version in its message.
- Security posture. Container scores change, because a pending update weighs by its group and no longer by its type. A posture threshold alert can recover or fire at the first scoring after the upgrade.
Update ranking
- The groups keep their thresholds: Critical from 81, Recommended from 31 to 80, Available below 31.
- The type of the update gives the base: patch 45, minor 40, major 20, new digest under the same tag 5. A new major version of a supported release line is Available.
- Support of the running version raises the score: at least 85 once it has ended, at least 65 when it ends within 30 days.
- With CVE enrichment (Pro and Personal), the highest severity among the CVEs the update fixes gives critical 90, high 65, medium 40 or low 20, plus 10 when the container is publicly exposed. A CVE counts when its fixed version is known and the update reported, or the later major version shown next to it, reaches that version. A CVE without a known fix does not change the score and stays listed with the CVEs of the container.
- Restarts during the last day still add up to 10. Breaking changes found in the changelog no longer count.
- The Updates page, the update badge of a container and the update detail are colored by group, not by type: a major update listed under Available is no longer red.
Current major version first
- When a newer version exists both inside the current major version and in a later one, the update reported is the one inside the current major version. The later one is shown next to it as Next major, and as
major_tagin the API. A container onpostgres:18.7with18.8and19.0published is reported as18.7 → 18.8, with19.0as the next major. - The same holds for a floating tag republished under the same name: the new digest is the update reported, with the later major version next to it.
- The update command and the changelog are those of the version reported.
- With
maintenant.update.trackset tominor,patchordigest, no next major is reported.
Support of official images
- For the official Docker Hub images of
postgres,mysql,mariadb,redis,mongoandnginx, maintenant reads the end of support of the running release line from endoflife.date, the source already used for operating systems. It is part of every edition. - The release line comes from the tag (
postgres:18.7,mysql:8.4.3,redis:7.2.5-alpine). A tag that does not name one, such aslatest,nginx:stable,mysql:8orredis:7, is not tracked. Images from another registry or publisher are not tracked either. - An update of a tracked image shows its release line and the time left, for instance
PostgreSQL 18: 3 y 11 mo left. - A Software lifecycle block on the Updates page lists every running container of these images, grouped by release line, with the time left before the end of support. It does not depend on update tracking: a pinned container, one with
maintenant.update.enabled: "false"or one whosetrackhides later versions is listed like the others. Ignored and archived containers are left out. - The dates come with the daily refresh of the support table, which now makes thirteen requests to endoflife.date instead of seven.
MAINTENANT_DISABLE_OS_EOL_REFRESHturns it off for operating systems and images alike, and the table embedded in the binary then applies.
Alerts
- The severity of
update_availableis set from the final score, after CVE enrichment: critical from 81, warning from 61, info below. - When the version reported for a container changes, for instance after a new release, its alert is resolved and raised again in the same scan with the new version. It used to stay resolved until the next scan.
- The alert details carry
major_tagwhen a later major version exists. - A container with a health check that has stopped is no longer reported as unhealthy: a one-shot job that exited with code 0 raises no
health_unhealthyalert. The alert of a container that was unhealthy and then stopped resolves with "Container stopped, its health check no longer runs".
Security posture
- The
updatescategory loses points per pending update by its group: Critical 25, Recommended 10, Available none. It used to lose 25 for a major update, 10 for a minor one and 5 for a patch. Its summary reads1 critical, 2 recommended. - The
image_agecategory ignores Available updates. With no Critical or Recommended update pending it scores 100.
API and MCP
- An update returned by
GET /api/v1/updatesandGET /api/v1/updates/container/{container_id}hasmajor_tagwhen a later major version exists, and asupportobject for a tracked image, with the same fields as the support object of a host operating system. GET /api/v1/updates/imageslists the running containers of the tracked images with the support status of their release line.- The MCP tool
get_updatesreturnsmajor_tagon updates and animageslist. - The
update.detectedevent carriesmajor_tag. It is sent once the scan has enriched its results, after theupdate.resolvedevents of the same scan.
Upgrading
Migration 48 runs at startup on SQLite and PostgreSQL. It adds major_tag to the pending updates and sets the open critical update_available alerts to info.
The scores stored by the previous version stay on the Updates page until the first scan, which starts shortly after startup.
The health fix is also in the agent binary. The server already handles an agent that has not been upgraded.
The Helm chart moves to 1.13.0, the same as the application version.
The full documentation is at docs.maintenant.dev.