Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[1.3.0] - 2026-06-04

A one-line digest after the per-version details, summarizing the releases scanned, security updates with severity totals, and breaking changes.
A "missing security fixes" warning when the resolved target lands below newer security releases, listing the versions you would skip.
composer typo3:check-updates now takes optional arguments: with none it uses the installed typo3/cms-core version and the latest release in that line; with only the current version it defaults the target to the latest. Auto-detected or defaulted values are confirmed before the check runs.

composer typo3:check-updates validates that both versions exist in the release line: an unknown target offers the latest instead, and an unknown current version is rejected with a hint.

Compatibility with Composer 2.9 / Symfony Console 8: the typo3:check-updates command no longer relies on the removed setName() / setDescription() methods, so it builds and runs on the latest PHP and Composer.

Bounded retry (up to 3 attempts) with exponential backoff and honored Retry-After header (capped at 5 s) on transient TYPO3 API issues, so a single hiccup no longer blocks composer update.
Per-version failure messages: when some versions fail to fetch, the others are still shown and each failure is categorized (network error, server error, not found, malformed response) with a retry suggestion.
Plugin output is now framed by a yellow TYPO3 Update Check header and a separator so users can see at a glance where the messages come from.
composer typo3:check-updates returns a non-zero exit code when every version fails, so CI can detect API outages.