v3.1

What's Changed

• Updates that need a new major of an installed package are now blocked when the project's composer.json or another installed package still holds that package back, e.g. silverstripe/asset-admin ^3 on a CMS 5 project. Packages that only the updated package requires can still move.
• Compare links for dev-branch installs start from the installed commit.

Full Changelog: v3...v3.1

v3

What's Changed

• The outdated report is now split by platform compatibility:
  • A table of updates that install on the current platform, showing the newest compatible version alongside the latest.
  • Packages with no compatible update are collapsed into a <details> block, with what blocks them (e.g. php ^8.3, acme/framework ^6).
• New php-version input, used when composer.json has no config.platform.php.
• New compatibility-packages input, listing packages whose installed major version updates must stay compatible with.
• The composer_outdated output has new columns and layout, so workflows that parse it may need updating.

Full Changelog: v2...v3

v2

What's Changed

• Refactored to use json output from composer outdated enriching the output for github repos, now including:
  • Github repo links.
  • Version comparison link, showing everything which has changed between your current version and the latest.
  • Slightly longer descriptive text, this is truncated short to avoid dropping to more than one line

Full Changelog: v1...v2

v1

Initial release

v0.1

Initial release