October 30 Is Today: Adobe Commerce Cloud's Dependency Deadline and What Happens If You Miss It

October 30 Is Today: Adobe Commerce Cloud's Dependency Deadline and What Happens If You Miss It
October 30, 2026
Category: Adobe Commerce ,

Adobe Commerce on Cloud stores on 2.4.4 to 2.4.9 must leave MariaDB 10.5, Elasticsearch and RabbitMQ 3.9 by October 30, 2026. Here's how to check your environments in ten minutes, and what to do if you're already late.
Book a Dependency Check

What's Changing on October 30?

Adobe now requires every Adobe Commerce on Cloud (PaaS) environment on 2.4.4 to 2.4.9 to run supported versions of its third-party services. Three are due on October 30, 2026, and five more on May 31, 2027. Adobe performs the upgrades through a support ticket, which it asks you to open at least 30 days ahead. On-premises stores and Adobe Commerce as a Cloud Service are not affected.

Service If you run Move to Due
MariaDB / Galera 10.5 or older 10.6 or later Oct 30, 2026
Elasticsearch Any version OpenSearch 2.19 (2.4.4, 2.4.5) or 3.x (2.4.6+) Oct 30, 2026
RabbitMQ 3.9 or older 3.13 or later Oct 30, 2026
PHP 8.1 or older 8.2 or later May 31, 2027
MariaDB / Galera Above 10.5, below 10.11 10.11 or later May 31, 2027
OpenSearch 1.x 2.19 (2.4.4, 2.4.5) or 3.x (2.4.6+) May 31, 2027
Redis 5 or older Valkey 8 or later May 31, 2027
RabbitMQ Above 3.9, below 3.13 4.3 or later May 31, 2027

Your Commerce version has its own, later dates: June 1, 2027 for 2.4.4 and 2.4.5, and June 1, 2028 for 2.4.6 and 2.4.7. On 2.4.4 or 2.4.5, Adobe's summary lists only October 30 for dependencies, so treat everything as due then until Adobe confirms otherwise.

Source: Adobe Experience League, Required actions and deadlines to secure Commerce environments, updated October 14, 2026.

Check Your Environment in 10 Minutes

  1. Commerce version. It's in the bottom-right corner of every Admin page. If it's hidden, run bin/magento --version.
  2. Service versions. In Cloud Console, open the project and environment, then the Containers tab, and click each service. Check production, staging and every integration environment. On Pro plans, trust the Console over .magento/services.yaml.
  3. What your code depends on. These show your search engine setting and any packages that talk to search, cache or the queue directly:
    • bin/magento config:show catalog/search/engine
    • composer show | grep -iE "elastic|opensearch|search|redis|amqp"

Worth knowing: developers can script step 2 with magento-cloud environment:relationships -p <project-id> -e <environment-id> and read each service's type.

What Needs Testing After the Upgrade

Most of these are simple version upgrades. Two are moves to different software, so they need real testing.

  • Elasticsearch to OpenSearch: search results, layered navigation, autocomplete and any third-party search module. Reindex with bin/magento indexer:reindex catalogsearch_fulltext.
  • Redis to Valkey (May 2027): Valkey uses the same protocol, so settings usually carry over. Test sessions, full-page cache clears and tools that look for "redis" by name.
  • PHP 8.1 to 8.2 (May 2027): older modules often use dynamic properties, which 8.2 deprecates. The Upgrade Compatibility Report finds them.

 our take: MariaDB 10.6 meets October 30, but it falls straight into the May 2027 group. If your Commerce patch level is tested with 10.11 (system requirements), ask for 10.11 in the same ticket and upgrade once.

Already Inside the 30-Day Window?

With seven days left, Adobe's 30-day notice period has passed. Its page doesn't say late tickets are refused, or that they'll be finished in time. This week:

  1. Open the ticket today. List every environment and service, with current and target versions.
  2. Ask for a short extension in writing, in the ticket and through your account team, with a realistic date.
  3. Upgrade staging first. Test checkout, search, cart, payments and integrations.
  4. Know what needs the Admin. Orders, refunds, price changes, content. Have a workaround ready.

What Happens If You Miss It

Adobe says it may take these steps on environments that miss the deadline:

  • Admin suspended: no Admin access for any user. The storefront stays online.
  • Traffic suspended: the storefront goes offline.
  • Decommissioned: if still non-compliant after traffic suspension, all data, environments and branches are permanently deleted.

Whatever your timeline, keep a recent database and media backup outside the Cloud project.

Do You Need a Partner?

Not always. Here's our honest view.

Open the ticket yourself if…

  • Your changes are minor version upgrades
  • You have no third-party search module or custom cache code
  • Staging matches production and you have time to test

Bring us in if…

  • You're moving off Elasticsearch with a third-party search module or a Hyvä storefront
  • Your ERP or CRM syncs run on queues or cron, like NetSuite or Epicor P21
  • You're out of time and need the ticket, testing and production window handled

How Evrig Runs a Dependency Check

  1. Inventory. We list every environment and service against both deadlines.
  2. Review. We check extensions and custom code tied to search, cache, the database or queues.
  3. Ticket. We draft it with you, with versions that won't need redoing in 2027 and an extension request if needed.
  4. Test. After Adobe upgrades staging, we test checkout, payments, search, Hyvä components and ERP syncs.
  5. Go live. We support the production window and give you a plan for May 2027.

Engagement Options

Upgrade Audit: A fixed-scope check of your environments, code and extensions, with the Adobe ticket drafted for you.

Book a Dependency Check

Support & Maintenance: We run the whole cycle and keep your stack current through 2027 and your next Commerce upgrade.

Talk to Support

Pricing depends on how many environments you have, how much custom search and cache code you run, and how many integrations need testing.

Why Evrig

Adobe Silver Partner: We work with Adobe Commerce Cloud every day, including its environments, support process and release cycle.

Hyvä Gold Partner: We know how search and Magewire components behave on a Hyvä storefront after a search engine change.

Integration specialists: NetSuite, Epicor P21 and HubSpot integrations are everyday work for us, so we test the syncs a queue or database change can break.

17+ years of integration work: Long enough to know which upgrades look small and aren't.

Final CTA

Seven days is enough to know where you stand.

Send us your Commerce version, Cloud plan and integrations. We'll check every environment against Adobe's dates and tell you what goes in the ticket.

Book a Dependency Check This Week