Adobe Commerce 2.4.5: quality and faster GraphQL

Released 9 August 2022, 2.4.5 added Apple Pay through Payment Services, cacheable sessionless GraphQL and PWA Studio 12.5 compatibility.

Adobe Commerce 2.4.5: quality and faster GraphQL

Adobe Commerce (Magento) 2.4.5 shipped on 9 August 2022. It builds on the 2.4.4 foundation rather than replacing it: security, quality, and some GraphQL work that headless builds actually feel.

Security and quality

Adobe bundled 290+ fixes for Magento Open Source and over 400 for Adobe Commerce, plus backported security improvements to older lines. reCAPTCHA coverage extended to the forms that get hit most often — Wish List Sharing, New Account and Gift Card. Accessibility fixes kept landing across key flows.

Dependencies

Composer 2.2, TinyMCE 5.10.2 and jQuery UI 1.13.1. Unglamorous, but current front-end and build dependencies mean fewer conflicts and a smoother time for whoever maintains the codebase.

Payments

Apple Pay became available through Adobe Payment Services, which makes it a configuration job rather than a bespoke integration. PayPal Pay Later expanded to Italy and Spain — a conversion lever in those two markets, if you sell there.

GraphQL

Schema rebuilds got faster, and a setting to disable session cookies for GraphQL means API responses can be cached properly at the edge on Fastly or Varnish. On a headless storefront that shows up in time-to-first-byte and in perceived speed on PLP and PDP.

PWA Studio

2.4.5 is compatible with PWA Studio 12.5, which brought an eventing framework for shopper behaviour analytics on the storefront. Useful if you have decoupled the front end and still want proper analytics coverage.

What this means for you

If you are on 2.4.4, this is a short upgrade. Benchmark your GraphQL flows before and after, and confirm edge caching does what you expect with sessionless requests. Rebuild front-end bundles so the dependency updates reach production. Test checkout properly, including Apple Pay via Payment Services and any third-party payment modules. And review reCAPTCHA coverage and rate limiting on the forms that attract bots.