The Open-Source Maintenance Calendar: Every End-of-Life Date Coming Up, and the Job Each One Creates

The next three months hold a cluster of dates that each create a job: WordPress 7.2 is scheduled for 8 December 2026, Drupal 10 reaches end of life on 9 December 2026, PHP 8.2 loses security support on 31 December 2026, PostgreSQL 14 gets its final release on 12 November 2026, and WooCommerce has announced that version 11.6 will need PHP 8.1 or newer. Below is the full dated table, the December cluster, and for each row what stops working, how to check which version you run, and what the maintenance job looks like.

This page is written for a business owner or IT lead who runs open-source software and wants to know which dates mean work. “End of life” (often shortened to EOL) means the project stops shipping fixes for that version, so any new security problem found in it stays unfixed on your server. Every date below was read on the project’s own site on 8 October 2026, and every row links to its source. A date we could not confirm there is left out. This is general information, not legal advice.

In this guide

• The full calendar, sorted by date, with the source on every row
• The December cluster, and why it needs one plan instead of five
• One short section per piece of software: what breaks, how to check your version, what the upkeep job is
• What a maintenance arrangement covers month to month
• How we keep this page current
• Questions people ask

Which open-source end-of-life dates matter in the next few months?

Most of them fall between mid-October 2026 and the end of the year, with a second group in February to June 2027. The table is sorted by date. Rows dated before 8 October 2026 are included because the job is still open for anyone who has not acted. Where a project gives only a month, we give only a month.

Date	Software	What happens on that date	Source
April 2026 (passed)	MySQL 8.0 (Oracle)	MySQL 8.0 reaches end of life. The last version is 8.0.46 (2026-04-21); Oracle encourages a move to MySQL 8.4 LTS or the latest Innovation release.	MySQL 8.0 release notes; Oracle Lifetime Support Policy
30 June 2026 (passed)	Mautic 5.2	Security support for the 5.2 long term release ends. Mautic sells paid Extended Long Term Support for it, running to 30 June 2028.	Mautic releases
6 July 2026 (passed)	MariaDB 10.6	Community end of life. This is MariaDB, a separate product from MySQL, with its own schedule.	MariaDB maintenance policy
11 August 2026 (passed)	Adobe Commerce 2.4.6	End of standard support. Extended support for 2.4.6 runs to 31 August 2027, and a security-only period to 31 May 2028.	Adobe Commerce lifecycle policy
September 2026 (passed)	Nextcloud 32	End of life, listed as 2026-09. Nextcloud 32 no longer receives bug fixes or security updates.	Nextcloud maintenance and release schedule
September 2026 (passed)	Odoo 17.0	End of standard support, listed as September 2026. Extended support is a paid option, on-premise for any version.	Odoo standard and extended support
30 September 2026 (passed)	Mautic 6.0	Security support for the 6.0 long term release ends. Extended Long Term Support to 30 September 2027 is listed.	Mautic releases
20 October 2026	WordPress 7.2	Beta 1, followed by betas on 27 October, 3 November and 10 November.	WordPress 7.2 Release Party Schedule
12 November 2026	PostgreSQL 14	Final release for version 14, after which it is unsupported.	PostgreSQL versioning policy
17 November 2026	WordPress 7.2	Release Candidate 1. RC 2 on 24 November, RC 3 on 1 December.	WordPress 7.2 Release Party Schedule
Week of 7 December 2026	Drupal 12 and 11.5	Drupal 12.0.0 and 11.5.0 are released. Security support ends for 11.3.x and 10.6.x.	Drupal core release schedule
8 December 2026	WordPress 7.2	Scheduled general release, after a dry run and 24-hour code freeze on 7 December.	WordPress 7.2 Release Party Schedule
9 December 2026	Drupal 10	Drupal 10 reaches end of life. Drupal 10.6 is the last minor release of Drupal 10.	Drupal core release schedule
31 December 2026	PHP 8.2	Security support ends. PHP 8.4 active support also ends on this date, with security fixes continuing to 31 December 2028.	php.net supported versions
31 December 2026	Mautic 4.4	Extended Long Term Support (the paid program) ends.	Mautic releases
February 2027 (planned)	WooCommerce 11.6	Requires PHP 8.1 or newer. Sites on PHP 7.4 or 8.0 can keep updating through 11.5 and not beyond.	WooCommerce developer blog, 29 September 2026
February 2027	Nextcloud 33	End of life, listed as 2027-02 (supported until 17 February 2027 in the schedule’s timeline). Nextcloud 34 follows in June 2027 and 35 in September 2027.	Nextcloud maintenance and release schedule
31 May 2027	Adobe Commerce 2.4.7	End of standard support. Extended support to 31 May 2028.	Adobe Commerce lifecycle policy
1 June 2027	Adobe Commerce on Cloud	Adobe states it will no longer maintain Cloud environments running unsupported Commerce versions, including suspending traffic to them.	Adobe Commerce lifecycle policy
April 2029	MySQL 8.4 LTS	Premier support ends. Extended support runs to April 2032.	Oracle Lifetime Support Policy
No date stated	Matomo 6	Still in beta. The latest pre-release on GitHub is 6.0.0-b5, published 4 October 2026, and the repository’s Composer file asks for PHP 8.1.0 or newer.	matomo-org/matomo releases

PHP 8.1 is no longer in the “currently supported versions” table on php.net as of 8 October 2026, which is why the WooCommerce row matters: a store still on PHP 7.4 or 8.0 is on an unsupported PHP and is about to be locked out of WooCommerce updates as well.

What is the December cluster, and why plan it as one job?

Five separate things land within about four weeks of each other: WordPress 7.2 on 8 December, Drupal 12 in the week of 7 December, Drupal 10 end of life on 9 December, PHP 8.2 security support ending on 31 December, and the Mautic 4.4 paid program ending the same day. Together they fall in the holiday period, so finish the preparation in November.

The dates to hold in mind: 12 November (PostgreSQL 14), 17 November (WordPress 7.2 RC 1, the point to start testing), the week of 7 December (Drupal 12), 8 December (WordPress 7.2), 9 December (Drupal 10 end of life) and 31 December (PHP 8.2 and Mautic 4.4).

Do not change the PHP version and the application version in the same window. For a WordPress site on PHP 8.2, test a newer PHP on a copy, move PHP first, confirm everything works, then take WordPress 7.2 a week or two after release. With two changes in one window, nobody knows which one broke the site, and a rollback undoes both.

What does the maintenance job look like for any date?

The same six steps apply to every row, and the sections below only describe what is specific to each piece of software.

1. Inventory. Write down every site and server, the application version, the PHP version, the database and its version, the hosting, and who owns it.
2. Test on a copy. Clone the site to a staging copy with real data, apply the upgrade there, and click through the paths that make money or serve members: login, checkout, forms, search, email.
3. Choose an upgrade window. Pick a low-traffic slot, tell the people who will notice, and decide in advance who is on hand.
4. Prepare a rollback plan. Take a full backup of files and database immediately before, and know how long a restore takes. A backup that has never been restored is a hope, not a plan.
5. Monitor afterwards. Watch error logs, uptime, and the key transactions for the first days, not the first hour.
6. Report. Write down what changed, what was tested, what was found, and what is next, in words the person paying the invoice can read.

WordPress 7.2: what changes on 8 December, and how do you check your version?

WordPress 7.2 is scheduled for 8 December 2026. The release team’s schedule has betas on 20 October, 27 October, 3 November and 10 November, release candidates on 17 November, 24 November and 1 December, and a dry run with a 24-hour code freeze on 7 December. The post says last-minute adjustments are possible, so recheck it before planning around a day.

What breaks sites is a plugin or theme written for older behaviour, and an automatic update that applies before anyone has tested it. To check your version, open the Dashboard, then Updates, or run this from the server:

wp core version
wp plugin list --fields=name,version,update

The job: inventory every plugin and the theme, test the release candidate on a staging copy from 17 November, decide whether automatic major updates stay on, and apply the final release in a planned window shortly after it ships. For how security patching works day to day, see The 2026 WordPress Vulnerability Wave, and Why Maintenance Is the Product, and for sites with member logins, WordPress Security Maintenance When Members Have Logins. We do not repeat them here.

PHP 8.2 and 8.4: what ends on 31 December, and how do you check your PHP version?

On php.net, PHP 8.2 gets security fixes until 31 December 2026, PHP 8.3 until 31 December 2027, PHP 8.4 until 31 December 2028 and PHP 8.5 until 31 December 2029. Active support (the phase where ordinary bug fixes ship) ends for 8.4 on 31 December 2026, for 8.5 on 31 December 2027. PHP 8.1 is no longer in the supported table.

PHP is the layer underneath WordPress, WooCommerce, Drupal, Magento, Mautic and Matomo, so a PHP end of life affects all of them at once. On an unsupported PHP the site keeps running, with security holes that will not be patched. To check your version:

php -v
wp eval 'echo PHP_VERSION;'

The job: find every site on 8.2 or older, test each on a copy under PHP 8.3 or 8.4 with error logging on, fix or replace plugins that raise deprecation notices or fatal errors, switch the version in a window, and watch the logs. Applications also set their own PHP floors, which is the next row.

WooCommerce 11.6: why does it need PHP 8.1?

The WooCommerce developer blog announced on 29 September 2026 that WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer. Stores on PHP 7.4 or 8.0 will see a dismissible admin notice in version 11.3 and can keep updating through 11.5, but cannot go beyond it without moving PHP. The post notes that WordPress normally blocks a plugin update when the server does not meet its PHP requirement, so a store on old PHP does not break on the day: it stops receiving WooCommerce updates, including security fixes.

To check, look at Tools, then Site Health, then Info, or at WooCommerce, then Status, which lists the PHP version and the WooCommerce version. From the server:

wp plugin get woocommerce --field=version
wp eval 'echo PHP_VERSION;'

The job is the PHP job above, with the store paths as the test list: add to cart, checkout with each payment method, coupons, tax, shipping rates, order emails, subscriptions and any extension that talks to a payment gateway.

MySQL and MariaDB: which one do you run, and what ended?

MySQL and MariaDB are two different products that share a history and a command-line client, which is why they are often confused. MySQL is Oracle’s. MariaDB is a separate project with its own versions and dates. Check which you have before you read any date.

For MySQL, the 8.0 release notes state: “As of April 2026, with version 8.0.46, MySQL 8.0 reaches End of Life (EoL).” Oracle’s lifetime support table lists MySQL 8.4 with premier support to April 2029 and extended support to April 2032. For MariaDB, mariadb.org lists community end of life for 10.6 as 6 July 2026, for 10.11 as 16 February 2028, for 11.4 as 29 May 2029, and for 11.8 as 4 June 2028.

mysql --version
wp db query "SELECT VERSION();"

The output of the version query says “MariaDB” in the string when it is MariaDB. A database upgrade is the riskiest job on this page. The job: take a dump and a file-level snapshot, restore it onto a separate server and run the application against the restored copy, run the upgrade there first, compare row counts and key queries, schedule the real upgrade with a tested way back, and keep the old server image until you are sure. Moving from 8.0 to 8.4 is the supported path Oracle names. Moving between MySQL and MariaDB is a migration, not an upgrade.

PostgreSQL 14: what happens on 12 November?

The PostgreSQL project lists 12 November 2026 as the final release for version 14. Version 13 reached its final release on 13 November 2025 and is marked unsupported. The page recommends always running the current minor release of your major version.

psql --version
psql -c "SHOW server_version;"

PostgreSQL does not upgrade in place across major versions the way a minor update does. The job: inventory every database and extension, rehearse a dump-and-restore or a pg_upgrade run on a copy, time the rehearsal so the real window has a known length, upgrade, run the application’s own tests against it, and keep the old cluster until the checks pass.

Drupal 10, 11 and 12: what happens in the week of 7 December?

Drupal’s schedule says Drupal 10 reaches end of life on 9 December 2026, that 10.6.0 is the last minor release of Drupal 10, and that in the week of 7 December 2026 Drupal 12.0.0 and 11.5.0 are released, with security support ending for 11.3.x and 10.6.x. The same schedule shows 12.0.0-beta1 in the week of 14 September and 12.0.0-rc1 in the week of 9 November. We did not find a Drupal 11 end-of-life date on that page, so none is shown in the table.

drush status
composer show drupal/core

A Drupal upgrade from 10 to 11 mostly turns on whether your contributed modules and custom code support the new version, and on the PHP version Drupal requires. Do not assume the module list is ready. The job: run the upgrade-readiness checks on a copy, replace or patch modules that have no newer release, test the paths editors and visitors use, and plan the cutover for before 9 December.

Magento Open Source and Adobe Commerce: what does Adobe actually say?

Adobe’s lifecycle policy covers Adobe Commerce. It describes three years of standard support from general availability and one extra year of extended support at no extra cost for Adobe Commerce customers on versions 2.4.6 and 2.4.7. The table lists 2.4.6 standard support ending 11 August 2026 and 2.4.7 on 31 May 2027. The page does not mention Magento Open Source at all, so we do not state a date for Magento Open Source here. If you run Magento Open Source, check your edition and your exact version against Adobe’s published information before relying on any date above.

The page also says that starting 1 June 2027 Adobe will no longer maintain Cloud environments running unsupported versions, and will suspend traffic to them, which takes the storefront offline. And it says Adobe does not provide fixes for third-party dependencies such as PHP, MariaDB, OpenSearch, Redis or RabbitMQ that reach end of life during the support period: you maintain those yourself.

bin/magento --version

The job: inventory the Magento version, patch level, extensions and every dependency, test the next version on a copy with real catalogue and order data, and treat the dependencies (PHP, database, search) as part of the same schedule.

Odoo, Nextcloud and Mautic: which versions are near their end?

Odoo. Odoo’s documentation says it supports every major version in two phases: standard support for the first three years, and extended support, which needs an additional fee, afterwards. Its table lists Odoo 17.0 (released November 2023) with end of standard support in September 2026, Odoo 18.0 in September 2027 (planned), Odoo 19.0 in September 2028 (planned) and Odoo 20.0, released in September 2026, in September 2029 (planned). You can upgrade from any version to a major version still under standard support, or one that reached the end of standard support less than six months ago, so a version 17 database is inside that window now and the window is closing.

Nextcloud. New major versions come out about every four months and are supported for about a year. On the maintenance schedule, 32 reached end of life in September 2026, 33 ends in February 2027, 34 in June 2027 and 35 in September 2027. Check your version in the admin settings overview or with sudo -u www-data php occ status on a standard install. Because each version lasts about a year, Nextcloud means upgrading at least yearly.

Mautic. Mautic’s release page lists 5.2 security support ending 30 June 2026, 6.0 ending 30 September 2026, and Extended Long Term Support, a paid program, for 4.4 ending 31 December 2026. It also states that security support covers Mautic itself, not core dependencies that are already end of life, such as Symfony or PHP. The release page lists PHP requirements by series: 5.x on PHP 8.1 to 8.3, 7.x on PHP 8.2 to 8.5. The page names a different 7.x release as the long term one in its text and in its table, so confirm which before planning to a minor version.

For all three, the job is the standard six steps with attention to the data: export the data and test the restore, upgrade a copy through each required step, check integrations (mail sending, tracking scripts, single sign-on), and keep the old install until the new one has run cleanly.

Matomo 6: is it out, and what does it need?

Matomo 6 is not a stable release as of 8 October 2026. The matomo-org/matomo repository shows 6.0.0-b5 marked as a pre-release, published on 4 October 2026, while the latest stable version is 5.14.1. The Composer file on the 6.x branch asks for PHP 8.1.0 or newer. We do not state a release date for Matomo 6, because we did not find one stated by Matomo.

The job today is small: stay current on 5.x, keep PHP at or above what 6 will need, and do not run a beta on the instance that produces your reporting. When a stable release ships, test it on a copy of the database first.

What does a maintenance arrangement cover month to month?

A maintenance arrangement turns this calendar into routine rather than emergencies. Our WordPress maintenance service describes updates tested before they go live, backups with restore drills, security monitoring, performance checks, uptime alerts and a monthly report. For the dates on this page, the month-to-month work is:

• A living inventory. Every site, version, PHP version, database and owner in one list, reviewed monthly.
• A staging copy for every change. Upgrades are rehearsed on a clone with real data before they touch production.
• Dated upgrade windows. Each end-of-life date gets a planned window well ahead of it, not a scramble in its last week.
• A tested rollback. A backup taken just before the change, and a known restore time.
• Dependency tracking. PHP, the database, search and cache layers are watched alongside the application, since vendors such as Adobe and Mautic say they do not patch end-of-life dependencies for you.
• Monitoring after the change. Logs, uptime and key transactions for days afterwards.
• A plain monthly report. What changed, what was tested, what is next.

The service page describes WordPress sites. For other software on this list, such as Drupal, Magento, Odoo, Nextcloud, Mautic or Matomo, we can describe the approach above, but ask us what applies to your stack before assuming it is covered.

How do we keep this page current?

Dates move: WordPress allows last-minute adjustments, and WooCommerce and Odoo mark some dates as planned. We update this page when a project changes a date, and every row carries its source so you can check it yourself. The date we last read each source is 8 October 2026. If a row is wrong by the time you read it, trust the linked source over this page and tell us. Rows we could not confirm on a primary source are left out, not guessed.

Questions people ask

What happens if you keep running software after its end-of-life date?

It keeps working, and that is the danger. After end of life the project stops shipping fixes, so a security problem found later stays open. Nextcloud’s schedule says end-of-life versions no longer receive bug fixes or security updates, and Adobe says it does not patch dependencies such as PHP that reach end of life.

Which date should you deal with first?

Whichever is closest and hardest to undo: PostgreSQL 14 on 12 November if you run it, then PHP 8.2 on 31 December, since PHP sits under everything else.

Should you update WordPress on the day 7.2 is released?

Test the release candidate on a copy from 17 November, then update in a planned window shortly after release. Do not change the PHP version and the WordPress version in the same window, so a problem can be traced to one cause.

Does WooCommerce 11.6 mean your store breaks in February?

Not on the day. Per the WooCommerce post, stores on PHP 7.4 or 8.0 can keep updating through 11.5 but cannot go further, so the store stops getting updates, including security fixes. Move PHP before then.

Is Magento Open Source covered by Adobe’s extended support?

Adobe’s lifecycle page does not mention Magento Open Source, so we cannot say. Check your edition and exact version against Adobe’s published information.

If you would rather have this calendar run for you than track it yourself, our WordPress maintenance plans cover tested updates, restorable backups, monitoring and a monthly report for WordPress sites, and you can read how maintenance and care plans differ before you decide. Tell us what you run and we will tell you which rows apply.