Adobe has updated its release and support schedules for Adobe Commerce (Magento). Three things changed: extended support for version 2.4.4, more security patching, and a paid extended support option for merchants who need one.
Longer support for 2.4.4
Adobe Commerce 2.4.4 receives support beyond the original schedule, which buys time for merchants planning an upgrade. That matters most at scale, where an upgrade is a coordination exercise as much as a technical one. The change also reflects how many merchants are still running 2.4.x, while still pointing them towards newer versions eventually.
More security patching
Adobe will ship additional security patches for supported versions, weighted towards critical vulnerabilities and anything being exploited in the wild. Those arrive through both the standard quality updates and an accelerated security-only track, so a critical fix does not have to wait for a scheduled quarterly release or carry a quarterly release's testing overhead.
Paid extended support
For merchants who need support past the standard timelines, there is now a paid programme:
extended security patches and quality fixes for specified versions
priority support queues and dedicated technical resources
custom backports of critical fixes and features
timelines shaped around the individual merchant
advance notice of upcoming maintenance and deprecations
It is aimed squarely at complex integration estates, and at teams whose own release cycles run long.
What this means for you
Extended timelines are planning windows, not permission to stop. If you are on 2.4.4 or earlier, you have more room than you did — use it to plan properly rather than to defer. If you are weighing up 2.4.5 or later, the performance and capability gains are the argument. And if the standard timeline genuinely does not fit your business or technical constraints, paid extended support is now a real option rather than a conversation.
Either way the useful move is the same: work out your upgrade readiness with whoever will be doing the work, early enough that the date is yours rather than Adobe's.
:quality(75))