PHP Release and Support Timeline - Active Support, Security Fixes, and End-of-Life Dates

First Published:
Last Updated:

When using PHP, you need to determine when bug fixes and security fixes will stop for the branch you are currently using. The "Supported Versions" page on php.net outlines these rules.

Each release branch of PHP is fully supported for two years from its initial stable release. During this period, bugs and security issues that have been reported are fixed and are released in regular point releases.
After this two year period of active support, each branch is then supported for two additional years for critical security issues only. Releases during this period are made on an as-needed basis: there may be multiple point releases, or none, depending on the number of reports.
Once the four years of support are completed, the branch reaches its end of life and is no longer supported.

These rules have not always been in their current form. The lifecycle established by an RFC in 2010 was three years, with two years of bug fixes and one year of security fixes only. An RFC in 2024 extended the security fix period by one year and aligned the end date to December 31. This RFC applied to 8.2 and later branches, and an additional year of security fixes was added for 8.1, resulting in an EOL date of December 31, 2025, for 8.1.

As of November 20, 2026, the "Supported Versions" page lists five branches: 8.2, 8.3, 8.4, 8.5, and 8.6. Branch 8.6 was first released as 8.6.0 on November 19, 2026. The security fixes for 8.2 are scheduled to end on December 31, 2026, and the active support for 8.4 is also scheduled to end on the same date.

This article presents a timeline detailing when each PHP branch was initially released and when active support and security fixes ended (or are scheduled to end), along with the source of each row's date. The two questions this timeline aims to answer are: what is the relationship between the EOL date and the date of the last release for each branch? And how did the rule changes in 2024 affect the dates for each branch?

Based on the available documentation, the answers are as follows. First, regarding EOL dates: the "Date" column on the "Unsupported Branches" page indicates the EOL date for that branch, and it does not necessarily correspond to the date of the last release. For 8.1, the last release, 8.1.34, was released 13 days before the EOL date. For 5.6, the last release, 5.6.40, was released 10 days after the EOL date. Secondly, concerning the rule changes: for five branches, from 7.1 to 8.0, the EOL date is exactly three years after the initial release. For five branches, from 8.2 to 8.6, the "Active Support Until" and "Security Support Until" dates in the "Supported Versions" table all fall on December 31.

This article only provides the dates for PHP branches and the sources for those dates. Information regarding new features in each version, the process for upgrading, and the end-of-life dates for PHP versions on various AWS services will be covered in separate articles and official documentation (a list of these topics is provided in the "Topics Covered in Other Articles" section). This article does not address security vulnerabilities or pricing.

Background and Method of Creating the PHP Release and Support Timeline

This section details the sources used to create the timeline and explains how the dates for each entry were determined. All sources were consulted as of November 20, 2026 (Japan Standard Time).

The Primary Sources Used in This Article, and What Became Rows

The rows of the timeline come from the following primary sources:

  • Supported Versions page (php.net): This page details the rules for support periods and includes a table listing "Currently Supported Versions." The table has five columns: Branch, Initial Release, Active Support Until, Security Support Until, and Notes. As of November 20, 2026, the table lists five entries, covering versions 8.2 through 8.6.

  • Unsupported Branches page (php.net): This page contains a table listing branches that are no longer supported. The table has four columns: Branch, Date, Last Release, and Notes. This article refers to this page as the "EOL page." As of November 20, 2026, the table lists entries from version 8.1 down to version 3.0.

  • Releases list (php.net): This list provides the version number and release date for each version. This article extracted the initial release date and the date of the last release for each branch from the JSON data returned by this list. The URL for this JSON data follows the format https://www.php.net/releases/?json&version=8.

  • Announcements (php.net): This article used announcements related to each version's release, as well as announcements for alpha, beta, and RC versions of upcoming branches. The dates for these announcements were extracted from the corresponding announcement pages.

  • RFCs and Timetable (wiki.php.net): This article used an RFC (Release Process) from 2010, an updated RFC (Release cycle update) from 2024, and the timetable for PHP 8.6 (the Timetable in PHP 8.6 Preparation Tasks).

  • ChangeLog (php.net): This log lists the changes for each version in the 8.x series and was used to check whether any version numbers are missing.

  • AWS Documentation: This included the AWS Elastic Beanstalk platform release schedule, the PHP page for AL2023, the AWS Lambda page listing Lambda Event Function runtimes, and the Runtime deprecation page of AWS Lambda. These were used to confirm the relationship between AWS dates and PHP release dates.

The items included in this timeline are the initial releases for each branch from 5.0 to 8.6, the end-of-life dates for each branch, the end of active support from 2024, two RFCs, the pre-releases of 8.6, two security releases in 2026, and the planned dates that had not yet arrived as of November 20, 2026. Many point releases have not been included. Branches 4.x and earlier are not included either. In other words, please note that the items on this timeline are not all releases of PHP, but are representative updates that I have picked out.

Branches, Point Releases, and Three States

In this article, a unit with its own support period, such as 8.2 or 5.6, is called a "branch." Releases within a branch that deliver fixes, such as 8.2.35 or 5.6.40, are called "point releases." The initial stable release of a branch is referred to as the "initial release." The version in the "Last Release" column on the EOL page is called the "last release."

The "Supported Versions" page describes the status of branches using three terms. This article also uses the three terms, in English, in the "Status" column of the tables.

Active support
A release that is being actively supported. Reported bugs and security issues are fixed and regular point releases are made.
Security fixes only
A release that is supported for critical security issues only. Releases are only made on an as-needed basis.
End of life
A release that is no longer supported. Users of this release should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities.

Different sources sometimes describe the same date in different words. For example, 2026-12-31 is the "Security Support Until" date for version 8.2 in the "Supported Versions" table. The announcement for 8.2.35 on 2026-10-21 describes the same date as follows:

PHP 8.2 reaches end of life on 31 December 2026 and will receive no further security fixes after that date.

This article treats the "Security Support Until" date as the EOL date for that branch.

Timeline Table Columns and Sources for the Dates

The timeline includes the following five columns:

  • Date — Represents the date associated with the row. All dates are written in the YYYY-MM-DD format.
  • Change — Indicates the type of change. The value will be one of seven options listed below.
  • What Happened — Describes the event or change. Where a source is quoted, the quotation is verbatim.
  • Date Source — Specifies the type of document from which the "Date" value was obtained. The value will be one of five options listed below.
  • Source — Refers to the specific document used as the basis for the row. This column may include documents beyond those used for the "Date Source".

The "Change" values are as follows:

  • Initial Release — The initial release of the branch.
  • End of Active Support — The date listed as "Active Support Until" in the "Supported Versions" table.
  • End of Life — The date listed as "Date" on the EOL page, or the "Security Support Until" date in the "Supported Versions" table.
  • Last Release — The branch's last release.
  • Security Release — A point release for security fixes.
  • Policy — An RFC that defines the release procedures and schedule.
  • Pre-release — Alpha, beta, or RC versions for the next branch.

The "Date Source" values are as follows:

  • Supported versions table — The table on the Supported Versions page, specifically the "Currently Supported Versions" section.
  • EOL page — The "Date" column on the Unsupported Branches page.
  • Releases list — The dates for each version in the Releases list.
  • Announcement — The dates of announcements on php.net's News section.
  • RFC — The "Date" entries on the RFC page on wiki.php.net.

For the "Date" values, in rows representing the initial release, the date corresponds to the earliest version within that branch, as listed in the Releases list. For versions 8.2 through 8.6, this date matches the "Initial Release" date in the Supported Versions table. In the End of Life rows, the date is the Date on the EOL page, and the "What Happened" column gives the last release and its date. For announcements and releases, the date refers to the announcement date. Planned entries that have not yet occurred are compiled in a separate table.

The php.net pages display dates in the format 8 Dec 2022, accompanied by relative notations such as in 1 month or 10 months ago. These relative notations change based on the date of access, so this article does not copy them.

When Dates or Version Numbers Differ Across Sources

Occasionally, different dates or version numbers may be recorded for the same event in different sources. This article lists such instances in the "Where the Dates Differ" table at the end of the timeline. The "Kind of Difference" column contains the following three values:

  • The sources disagree — The sources provide different dates for the same type of event.
  • Different kinds of dates — The sources record different types of dates. For example, the date on the EOL page and the release date of the last release.
  • Same date, different version number — While the dates in the sources match, the version number listed differs from what the reader might expect.

As of November 20, 2026, this article has not identified any instances that fall under the category of The sources disagree. This article does not speculate about why sources record different dates or version numbers unless the sources themselves say why.

Topics Covered in Other Articles

This article will defer to other articles covering the following topics:

  • Details regarding the release and retirement dates for the PHP platform branches within AWS Elastic Beanstalk can be found in AWS History and Timeline regarding AWS Elastic Beanstalk. This article places only two examples, 8.1 and 8.2, next to the upstream dates in the "Where the AWS Dates Differ" section.
  • Information on the support lifecycle for each version of Amazon Linux and its associated packages can be found in Amazon Linux History and Timeline.
  • The end-of-support and end-of-life dates for various runtimes and engines across AWS services are detailed in AWS End-of-Support and EOL Reference.
  • Information on new features for each version and changes introduced when upgrading versions can be found on php.net's Migration pages (for example, "Migrating from PHP 8.4.x to PHP 8.5.x"). This article does not list features.

PHP Release and Support Historical Timeline (Updates from July 13, 2004)

The following three tables constitute the main timeline. Following these tables are the "Scheduled" table, which lists the planned dates as of November 20, 2026, and the "Where the Dates Differ" table, which lists events with differing dates or version numbers across various sources. Each table's columns are defined as described in the previous section. All data was referenced as of November 20, 2026.

Index:

  • 2004–2014 - The period during which versions 5.0 through 5.6 were released, the 2010 RFC established a three-year lifecycle, and versions 5.0 through 5.3 reached their end of life.
  • 2015–2023 - The period during which versions 7.0 through 8.3 were released, and versions 5.4 through 8.0 reached their end of life.
  • 2024–2026 - The period when the 2024 RFC introduced changes to the process, versions 8.4 through 8.6 were released, and version 8.1 reached its end of life.
  • Scheduled - Planned dates that had not yet arrived as of November 20, 2026.
  • Where the Dates Differ - A list of events with differing dates or version numbers across various sources.

* You can sort the table by clicking on the column name.

2004–2014 — From 5.0 to 5.6

DateChangeWhat HappenedDate SourceSource
2004-07-13Initial ReleaseVersion 5.0 was released. This is the first row of this article's timeline.Releases listReleases (PHP)
2005-09-05End of LifeVersion 5.0 reached its end of life. The last release is 5.0.5, and the Releases list also gives the date as 2005-09-05.EOL pageUnsupported Branches, Releases (PHP)
2005-11-24Initial ReleaseVersion 5.1 was released.Releases listReleases (PHP)
2006-08-24End of LifeVersion 5.1 reached its end of life. The last release is 5.1.6, and the Releases list also gives the date as 2006-08-24. This is 9 months after the initial release.EOL pageUnsupported Branches, Releases (PHP)
2006-11-02Initial ReleaseVersion 5.2 was released.Releases listReleases (PHP)
2009-06-30Initial ReleaseVersion 5.3 was released.Releases listReleases (PHP)
2010-11-22PolicyRelease Process RFC. This is the date in the Date row of the RFC page; the Version is 0.6 and the Status is Accepted. The RFC established a one-year release cycle and a three-year lifecycle, with two years dedicated to bug fixes and one year for security fixes only.RFCRequest for Comments: Release Process
2011-01-06End of LifeVersion 5.2 reached its end of life. The last release is 5.2.17, and the Releases list also gives the date as 2011-01-06.EOL pageUnsupported Branches, Releases (PHP)
2012-03-01Initial ReleaseVersion 5.4 was released.Releases listReleases (PHP)
2013-06-20Initial ReleaseVersion 5.5 was released.Releases listReleases (PHP)
2014-08-14End of LifeVersion 5.3 reached its end of life. The last release is 5.3.29, and the Releases list also gives the date as 2014-08-14. This was approximately 5 years and 1 month after the initial release.EOL pageUnsupported Branches, Releases (PHP)
2014-08-28Initial ReleaseVersion 5.6 was released.Releases listReleases (PHP)

2015–2023 — From 7.0 to 8.3

For five branches, from 7.1 to 8.0, the "End of Life" (EOL) date is exactly three years after the initial release. This article found this relationship by comparing the dates in two sources.

DateChangeWhat HappenedDate SourceSource
2015-09-03End of LifeVersion 5.4 reached its end of life. The last release is 5.4.45, and the Releases list also gives the date as 2015-09-03.EOL pageUnsupported Branches, Releases (PHP)
2015-12-03Initial ReleaseVersion 7.0 was released. Version 6 is not listed on the EOL page, and the JSON of the Releases list also returns Unknown version for version 6.Releases listReleases (PHP)
2016-07-21End of LifeVersion 5.5 reached its end of life. The last release is 5.5.38, and the Releases list also gives the date as 2016-07-21.EOL pageUnsupported Branches, Releases (PHP)
2016-12-01Initial ReleaseVersion 7.1 was released.Releases listReleases (PHP)
2017-11-30Initial ReleaseVersion 7.2 was released.Releases listReleases (PHP)
2018-12-06Initial ReleaseVersion 7.3 was released.Releases listReleases (PHP)
2018-12-31End of LifeVersion 5.6 reached its end of life. This is approximately 4 years and 4 months after its initial release. The last release, 5.6.40, has a release date of 2019-01-10 in the Releases list, which is 10 days after the date listed on the EOL page.EOL pageUnsupported Branches, Releases (PHP)
2019-01-10End of LifeVersion 7.0 reached its end of life. The last release is 7.0.33, and the Releases list also gives the date as 2019-01-10, approximately 3 years and 1 month after its initial release.EOL pageUnsupported Branches, Releases (PHP)
2019-11-28Initial ReleaseVersion 7.4 was released.Releases listReleases (PHP)
2019-12-01End of LifeVersion 7.1 reached its end of life, exactly 3 years after its initial release. The last release, 7.1.33, has a release date of 2019-10-24 in the Releases list.EOL pageUnsupported Branches, Releases (PHP)
2020-11-26Initial ReleaseVersion 8.0 was released.Releases listReleases (PHP)
2020-11-30End of LifeVersion 7.2 reached its end of life, exactly 3 years after its initial release. The last release, 7.2.34, has a release date of 2020-10-01 in the Releases list.EOL pageUnsupported Branches, Releases (PHP)
2021-11-25Initial ReleaseVersion 8.1 was released.Releases listReleases (PHP)
2021-12-06End of LifeVersion 7.3 reached its end of life, exactly 3 years after its initial release. The last release, 7.3.33, has a release date of 2021-11-18 in the Releases list.EOL pageUnsupported Branches, Releases (PHP)
2022-11-28End of LifeVersion 7.4 reached its end of life, exactly 3 years after its initial release. The last release, 7.4.33, has a release date of 2022-11-03 in the Releases list.EOL pageUnsupported Branches, Releases (PHP)
2022-12-08Initial ReleaseVersion 8.2 was released. The "Initial Release" date in the "Supported Versions" table is also listed as 8 Dec 2022.Releases listReleases (PHP), Supported Versions
2023-11-23Initial ReleaseVersion 8.3 was released. The "Initial Release" date in the "Supported Versions" table is also listed as 23 Nov 2023.Releases listReleases (PHP), Supported Versions
2023-11-26End of LifeVersion 8.0 reached its end of life, exactly 3 years after its initial release. The last release, 8.0.30, has a release date of 2023-08-03 in the Releases list.EOL pageUnsupported Branches, Releases (PHP)

2024–2026 — The 2024 RFC, 8.4 Through 8.6, and the End of Life of 8.1

DateChangeWhat HappenedDate SourceSource
2024-03-21PolicyRelease cycle update RFC. This is the date in the Date row of the RFC page; the Version is 0.2 and the Status is Accepted. It includes a proposal to extend the security support period by one year and align the end of bug fixes and security fixes to December 31. Voting concluded on April 29th at noon (UTC), and all six proposals received majority approval.RFCPHP RFC: Release cycle update
2024-11-21Initial ReleaseVersion 8.4 was released. The announcement was titled PHP 8.4.1 Released!, and the smallest version of 8.4 in the Releases list is also 8.4.1. The "Supported Versions" table lists the initial release as 21 Nov 2024.Releases listPHP 8.4.1 Released!, Releases (PHP), Supported Versions
2024-12-31End of Active SupportActive support for version 8.2 ended. This date is listed in the "Supported Versions" table as the end of active support.Supported versions tableSupported Versions
2025-11-20Initial ReleaseVersion 8.5 was released. The announcement was titled PHP 8.5.0 Released!.Releases listPHP 8.5.0 Released!, Releases (PHP)
2025-12-18Last Release8.1.34, the last release of 8.1, was released. The announcement stated This is a security release.AnnouncementPHP 8.1.34 Released!
2025-12-31End of LifeVersion 8.1 reached its end of life (EOL). The EOL page lists 8.1.34 as the last release. This is a little over four years and one month after the initial release, and is the result of the 2024 RFC adding one year of security fixes to 8.1.EOL pageUnsupported Branches, PHP RFC: Release cycle update
2025-12-31End of Active SupportActive support for version 8.3 ended.Supported versions tableSupported Versions
2026-07-02Pre-releaseAlpha 1 for version 8.6.0 was released.AnnouncementPHP 8.6.0 Alpha 1 available for testing
2026-08-13Pre-releaseBeta 1 for version 8.6.0 was released. In the timetable, this date is also the soft feature freeze.AnnouncementPHP 8.6.0 Beta 1 is available for testing, PHP 8.6 Preparation Tasks
2026-09-24Pre-releaseRelease Candidate (RC) 2 for version 8.6.0 was released. In the timetable, the RC1 row reads (skipped, explanation). The announcement for RC2 referred to it as the first RC.AnnouncementPHP 8.6.0 RC2 available for testing, PHP 8.6 Preparation Tasks
2026-10-08Pre-releaseRC3 for version 8.6.0 was released.AnnouncementPHP 8.6.0 RC3 available for testing
2026-10-21Security ReleaseVersions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 were released. The announcement described these as security releases addressing two critical vulnerabilities. Security fixes were also released for versions 8.2 and 8.3 during their security-only support period. The announcement for 8.2.35 states that 8.2 reaches end of life on 2026-12-31.AnnouncementPHP 8.2.35 Released!, Releases (PHP)
2026-10-21Pre-releaseRC4 for version 8.6.0 was released.AnnouncementPHP 8.6.0 RC4 available for testing
2026-11-05Pre-releaseRC5 for version 8.6.0 was released. The announcement stated that the next release is scheduled for GA on November 19, 2026.AnnouncementPHP 8.6.0 RC5 available for testing
2026-11-12Pre-releaseRC7 for version 8.6.0 was released. The timetable lists RC6 and RC7 as RC releases that were not planned, and the RC6 row reads tagged but then skipped. The announcement for RC7 refers to it as the fifth release candidate.AnnouncementPHP 8.6.0RC7 available for testing, PHP 8.6 Preparation Tasks
2026-11-19Security ReleaseVersions 8.5.13, 8.4.28, 8.3.37, and 8.2.36 were released. All four announcements state This is a security release. The advance notice on 2026-11-18 rated the highest severity as CRITICAL.AnnouncementPHP 8.2.36 Released!, Upcoming Critical PHP Security Release
2026-11-19Initial Release8.6 was released. The title of the announcement is PHP 8.6.0 Released!, and the smallest version for 8.6 in the Releases list is also 8.6.0. The Initial Release in the Supported Versions table is 19 Nov 2026.Releases listPHP 8.6.0 Released!, Releases (PHP), Supported Versions

Scheduled Dates as of November 20, 2026

The rows in the following table represent dates that had not yet occurred as of November 20, 2026. Please note that schedules are subject to change. Rows with dates after December 31, 2026, correspond to the dates listed in the "Supported Versions" table and are not presented as guarantees of support up to those dates.

DateChangeWhat HappenedDate SourceSource
2026-12-31End of LifeScheduled end date for security support for version 8.2. The announcement for 8.2.35 also gives this date as the end of life (EOL) for version 8.2.Supported versions tableSupported Versions, PHP 8.2.35 Released!
2026-12-31End of Active SupportScheduled end date for active support for version 8.4.Supported versions tableSupported Versions
2027-12-31End of LifeScheduled end date for security support for version 8.3.Supported versions tableSupported Versions
2027-12-31End of Active SupportScheduled end date for active support for version 8.5.Supported versions tableSupported Versions
2028-12-31End of LifeScheduled end date for security support for version 8.4.Supported versions tableSupported Versions
2028-12-31End of Active SupportScheduled end date for active support for version 8.6.Supported versions tableSupported Versions
2029-12-31End of LifeScheduled end date for security support for version 8.5.Supported versions tableSupported Versions
2030-12-31End of LifeScheduled end date for security support for version 8.6.Supported versions tableSupported Versions

Where the Dates Differ

EventDates by SourceKind of Difference
5.6 EOLThe EOL page lists the date as 2018-12-31. The last release, 5.6.40, is dated 2019-01-10 in the Releases list, 10 days later.Different kinds of dates
8.1 EOLThe EOL page lists the date as 2025-12-31. The last release, 8.1.34, is dated 2025-12-18 in the Releases list and the announcement, 13 days earlier.Different kinds of dates
7.1 to 8.0 EOLThe EOL page lists the date as exactly 3 years after the initial release. The last release came out 18 to 115 days before that date. The dates are listed in each row of the timeline.Different kinds of dates
8.4 Initial ReleaseThe "Supported Versions" table lists the initial release as 2024-11-21. The announcement on that date was titled PHP 8.4.1 Released!. The Releases list and the ChangeLog both have 8.4.1 as the smallest version of 8.4. The announcement for RC4 on 2024-11-07 states 8.4.0, RC4.Same date, different version number

This article does not speculate about why the version number of the 8.4 initial release is 8.4.1, because the sources do not say. The missing version number is not limited to 8.4.0. As of 2026-11-20, the Releases list, the ChangeLog, and the announcements have no versions 8.0.4, 8.3.5, 8.3.18, 8.3.34, or 8.4.9.

The release candidate (RC) numbers for 8.6 also differ from the ordinal numbers in the announcements. The RC1 row in the timetable reads (skipped, explanation), and the announcement on 2026-09-24 reads:

The PHP team is pleased to announce the first release candidate of PHP 8.6.0, RC2. It is not a typo: a mistake was made while packaging RC1, so RC2 was released instead.

The announcement for RC5 on 2026-11-05 refers to RC5 as the fourth release candidate. The announcement for RC7 on 2026-11-12 refers to RC7 as the fifth release candidate. The timetable describes RC6 as tagged but then skipped. This article's timeline lists the RC rows using the number from the announcement titles.

Current Overview of PHP Releases and Support

This section summarizes the status of each PHP branch as of November 20, 2026, outlines the support policy and the 2024 change to it, and clarifies the differences from the AWS dates.

Supported Branches as of November 20, 2026

The following figure illustrates the period from initial release to end of life (EOL) for branches 8.0 through 8.6. Branches 8.2 through 8.6 are divided into two periods, Active support and Security fixes only, by the dates in the Supported Versions table. Branches 8.0 and 8.1 are drawn as a single bar up to the Date on the EOL page. The red vertical line in the figure represents the verification date, 2026-11-20.

PHP Branch Lifecycle from 8.0 to 8.6
PHP Branch Lifecycle from 8.0 to 8.6
The following table shows the five rows of the Supported Versions table as of 2026-11-20. The Latest Release column displays the most recent release and its date from the Releases list.

* You can sort the table by clicking on the column name.

BranchInitial ReleaseActive Support UntilSecurity Support UntilLatest Release (as of November 20, 2026)Status (as of November 20, 2026)
8.62026-11-192028-12-312030-12-318.6.0 (2026-11-19)Active support
8.52025-11-202027-12-312029-12-318.5.13 (2026-11-19)Active support
8.42024-11-212026-12-312028-12-318.4.28 (2026-11-19)Active support
8.32023-11-232025-12-312027-12-318.3.37 (2026-11-19)Security fixes only
8.22022-12-082024-12-312026-12-318.2.36 (2026-11-19)Security fixes only

In the five rows from the Supported Versions table, "Active Support Until" is December 31 of the year two years after the initial release, and "Security Support Until" is December 31 two years after that. This relationship is what this article reads from the dates in the table.

Ended Branches

The following table adds the initial release date and the date of the last release from the Releases list to the rows for 5.0 through 8.1 on the EOL page. The "Initial Release to EOL Date" column is the duration that this article calculated from the initial release and the EOL date.

* You can sort the table by clicking on the column name.

BranchInitial ReleaseEOL Date (EOL Page)Last ReleaseRelease Date of the Last ReleaseInitial Release to EOL Date
8.12021-11-252025-12-318.1.342025-12-184 years, 1 month, 6 days
8.02020-11-262023-11-268.0.302023-08-03Exactly 3 years
7.42019-11-282022-11-287.4.332022-11-03Exactly 3 years
7.32018-12-062021-12-067.3.332021-11-18Exactly 3 years
7.22017-11-302020-11-307.2.342020-10-01Exactly 3 years
7.12016-12-012019-12-017.1.332019-10-24Exactly 3 years
7.02015-12-032019-01-107.0.332019-01-103 years, 1 month, 7 days
5.62014-08-282018-12-315.6.402019-01-104 years, 4 months, 3 days
5.52013-06-202016-07-215.5.382016-07-213 years, 1 month, 1 day
5.42012-03-012015-09-035.4.452015-09-033 years, 6 months, 2 days
5.32009-06-302014-08-145.3.292014-08-145 years, 1 month, 15 days
5.22006-11-022011-01-065.2.172011-01-064 years, 2 months, 4 days
5.12005-11-242006-08-245.1.62006-08-249 months
5.02004-07-132005-09-055.0.52005-09-051 year, 1 month, 23 days

In the 5.x branches, many rows have the same EOL date and last release date. From 7.1 to 8.0, the EOL date is later than the last release, occurring exactly three years after the initial release. Version 8.1 is a branch that received a one-year extension as determined by an RFC in 2024, and its EOL date is December 31.

The Policy at a Glance

The rules on the "Supported Versions" page can be summarized into the following three points:

  • 2 Years of Active Support: For the first two years from the initial release, bugs and security issues are addressed, and regular point releases are provided.
  • 2 Years of Security Fixes Only: In the subsequent two years, only critical security issues will be resolved. Releases will be issued only when necessary, and there may be none at all.
  • End of Life (EOL) after 4 Years: After four years of support, the branch reaches its end of life and will no longer be supported.

However, the dates listed in the "Supported Versions" table do not correspond exactly to two and four years from the initial release. This is because the 2024 RFC aligned the end dates with December 31. You should verify the specific dates for your branch in the "Supported Versions" table.

During the "security fixes only" period, critical fixes will also be released. For example, on October 21, 2026, releases were issued for versions 8.2 and 8.3 to address two critical vulnerabilities. This article does not cover the details of those vulnerabilities.

How the Policy Changed in 2024

The RFC (Release Process) established in 2010 defined the release cycle as follows:

Yearly release cycle
3 years release life cycle
2 years bug fixes only
1 year security fixes only

The end-of-life (EOL) dates for versions 7.1 through 8.0 are exactly three years after their initial release. This matches those three years. The duration of the 5.x branches varies significantly, ranging from 9 months to just over 5 years, depending on the branch.

The 2024 RFC (Release cycle update) presented six proposals regarding the release cycle, all of which passed by vote. The following table outlines the titles of each proposal as described in the RFC, along with the final voting results.

ProposalYesNo
Allow features that do not require an RFC in the beta period340
Disallow New Features in Release Candidates and Bug Fix releases320
Reduce number of RCs to Four303
Extend Security Support by One Year310
Allowing recent regression fixes during security support300
Extend Releases Cycle to End of Year330

Two proposals directly relate to the support period: "Extend Security Support by One Year" and "Extend Releases Cycle to End of Year." The RFC describes the first proposal as follows:

This change will extend release cycle to 4 years: 2 years of bug fixes, and 2 years of security fixes.

The rationale and details of the second proposal are as follows:

Right now, PHP comes out of normal or security release 2 or 3 years after the first GA release.
This means that the date shifts around, which is hard to keep track of. We propose to align the
end of bug fix and security releases with the end of the year, December 31st.
If a GA was delayed until early in a new year due to issues found during the release
candidate period, then the December 31st end date would not move a whole new year further.

The RFC specifies the branches to which these changes will be applied:

The changes will apply immediately on the all currently supported branches from PHP 8.2. It also means that PHP 8.1 would get an extra year of security fixes if the proposal is accepted.

The EOL date for version 8.1 is 2025-12-31. The EOL date for version 8.0, 2023-11-26, precedes the date of the RFC (2024-03-21) listed in the "Date" row.

Regarding the extended period for security fixes only, there is one caveat concerning Windows builds. The RFC states that updates to ABI incompatible versions of dependent libraries provided for Windows builds will not be included in this change.

The proposal does not include the updating of ABI incompatible versions of dependent libraries provided for Windows builds as this can add significantly more load.
This means that Windows users should track security changes in dependant libraries, if they want to keep using PHP in its second year of security support. This is just for Windows as we don't build dependent libraries for Linux and other systems: this the job of distributions to handle.

An example for version 8.4, as outlined in the RFC, indicates this transition with the entry for 2027-12-31.

Dec 31 2026: End of Bug Fix Releases — Start of Security Releases
Dec 31 2027: End of fixing regressions in Bug Fix releases — ABI incompatible versions of dependent libraries on Windows will no longer be updated.
Dec 31 2028: End of Security Releases

The timetable for version 8.6 planned four RCs (RC2 through RC5), aligning with the RFC to reduce the number of RCs to four (RC1 was skipped). The timetable lists RC6 and RC7 on 2026-11-12 as RC releases that were not planned. RC6 was tagged but then skipped, and RC7 was the one released.

Where the AWS Dates Differ

The dates for PHP as described in AWS documentation differ from the dates used in upstream PHP. This article does not represent AWS dates as PHP dates.

The page detailing the Elastic Beanstalk platform release schedule states the reasons for retiring platform branches as follows:

We must retire a platform branch when one of its components reaches End of Life (EOL).

As of November 20, 2026, comparing the rows for PHP 8.1 and PHP 8.2 on this page with the upstream EOL dates, the following information is presented:

BranchUpstream PHP End of LifeElastic Beanstalk Retirement Date (AWS)Days After Upstream End of Life
8.12025-12-312026-04-16 (PHP 8.1 AL2023 and PHP 8.1 AL2, retired)106
8.22026-12-31 (scheduled)2027-03-31 (PHP 8.2 AL2023, target retirement date)90

Upstream PHP End of Life vs. Elastic Beanstalk Retirement
Upstream PHP End of Life vs. Elastic Beanstalk Retirement
In both cases, the Elastic Beanstalk retirement date is later than the upstream PHP EOL date. The same page states that the target date for releasing the PHP 8.6 platform branch for Amazon Linux 2023 is January 2027. For the table of upcoming releases, the page notes These dates are tentative and subject to change. For a complete history and timeline regarding AWS Elastic Beanstalk, please refer to AWS History and Timeline regarding AWS Elastic Beanstalk.

The PHP page for AL2023 states the following as of November 20, 2026:

AL2023 currently provides the PHP programming language, versions 8.1, 8.2, 8.3, 8.4, and 8.5. Each version is supported for same period of time as upstream PHP.

This list includes PHP 8.1, which reached its upstream end of life on December 31, 2025. For a detailed history and timeline of each Amazon Linux version, please refer to Amazon Linux History and Timeline.

As of November 20, 2026, neither the "Supported runtimes" table on the Lambda Event Function runtimes page of AWS Lambda nor the "Deprecated runtimes" table on the Runtime deprecation page lists PHP (Documentation does not list). The runtimes page names PHP in only one place: an example of including a language runtime in the function's deployment package or in a layer and using it with an OS-only runtime (bring your own language, BYOL).

Third-party runtimes such as Bref for PHP use this approach.

For other languages and language versions, the same page recommends creating a customer-managed runtime. A What's New post dated November 18, 2026, announced customer-managed runtimes and stated that the existing custom runtimes feature has been renamed "bring your own language."

The end-of-support dates for each Lambda runtime are covered in the AWS End-of-Support and EOL Reference.

Frequently Asked Questions about PHP Releases and Support

What gets fixed during the two security-only years of a PHP branch?

According to the Supported Versions page, after the initial two years of active support for a PHP branch, only critical security issues are addressed. Releases are issued only when necessary, and there may be multiple releases, or none at all. On October 21, 2026, versions 8.2 and 8.3, which receive only security fixes, saw the release of 8.2.35 and 8.3.36 to address two critical vulnerabilities. On November 19, 2026, the security releases 8.2.36 and 8.3.37 were also released. For Windows builds, according to the 2024 RFC, during the second year of receiving only security fixes, updates to versions of dependent libraries that are not ABI-compatible will not be implemented.

Why does PHP 8.1 reach end of life on December 31, 2025, more than four years after its first release?

This is due to the 2024 RFC (Release cycle update), which extended the period for security fixes by one year and aligned the end dates with December 31. The RFC stated that the changes would apply to branches 8.2 and later, and also added one year of security fixes for PHP 8.1. PHP 8.1 was first released on November 25, 2021, and its end-of-life date is listed as December 31, 2025. The end of life of PHP 8.0 is November 26, 2023, exactly three years after its initial release.

Does PHP 8.2 really reach end of life on December 31, 2026?

As of November 20, 2026, it is a planned date. The "Supported Versions" table lists the security support for 8.2 as ending on December 31, 2026, and the announcement for version 8.2.35 (dated October 21, 2026) also states that 8.2 will reach its end of life on that date, after which it will no longer receive security fixes. Active support for 8.4 is also scheduled to end on the same date. This article will be updated to confirm the status after that date.

When was PHP 8.6 released, and when will its support end?

PHP 8.6 was released on November 19, 2026. The title of the announcement is PHP 8.6.0 Released!. As of November 20, 2026, the "Supported Versions" table lists the active support for 8.6 as ending on December 31, 2028, and the security support as ending on December 31, 2030. Both are planned dates.

Why is there no PHP 8.4.0 in the releases list?

As of November 20, 2026, the stable version 8.4.0 is not found in the Releases list, the ChangeLog, or any announcements. The announcement dated November 21, 2024, is titled PHP 8.4.1 Released!, and the "Initial Release" for version 8.4 in the "Supported Versions" table is also listed as November 21, 2024. Release candidate (RC) versions were released under the name "8.4.0," such as 8.4.0, RC4. This article does not speculate on the reason, as the available materials do not provide one.

Does AWS Elastic Beanstalk retire PHP 8.2 on the same date as upstream PHP?

No. As of November 20, 2026, the Elastic Beanstalk platform release schedule gives March 31, 2027, as the target retirement date for PHP 8.2 AL2023. This is 90 days after the upstream PHP 8.2 end-of-life date of December 31, 2026. For PHP 8.1, the upstream end of life was December 31, 2025, and the Elastic Beanstalk retirement was April 16, 2026. Please refer to the AWS History and Timeline regarding AWS Elastic Beanstalk for a complete overview of Elastic Beanstalk's dates.

Summary

This timeline begins with 5.0 on July 13, 2004, in the Releases list. As of November 20, 2026, the Supported Versions table lists five branches: 8.2 through 8.6, while the EOL page lists branches from 8.1 through 3.0.

⇒ A branch gets two years of active support and two years of security fixes only, and reaches end of life after four years. The 2024 RFC (Release cycle update) established this policy. The policy in the 2010 RFC (Release Process) was three years, and the EOL dates of 7.1 through 8.0 fall exactly three years after the initial release.

⇒ The 2024 RFC aligned the end dates with December 31 and also added one year to 8.1. The "Active Support Until" and "Security Support Until" dates in the Supported Versions table for branches 8.2 through 8.6 all fall on December 31. The EOL date for version 8.1 is December 31, 2025, which is approximately four years and one month after its initial release.

⇒ The dates listed on the EOL page do not always correspond to the date of the last release. Version 8.1's last release, 8.1.34, was released thirteen days before its EOL date, while version 5.6's last release, 5.6.40, was released ten days after. The initial release version for 8.4 was 8.4.1.

⚠ As of November 20, 2026, some rows are still planned. The EOL of 8.2 and the end of active support of 8.4 are planned for December 31, 2026. The end dates for versions 8.3 through 8.6 are also planned dates listed in the Supported Versions table. The retirement dates for AWS Elastic Beanstalk are separate from the upstream EOL dates. All information is current as of November 20, 2026.

This timeline will be updated as PHP releases and the PHP release cycle continue to evolve.

In addition, there are related history-and-timeline articles on this site, so please have a look if you are interested.


References:



References:
Tech Blog with curated related content

Written by Hidekazu Konishi