Skip to content

Commit

Permalink
DEP Limit PHP support for CMS 6
Browse files Browse the repository at this point in the history
  • Loading branch information
GuySartorelli committed Aug 19, 2024
1 parent 4fda778 commit 676142e
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 9 deletions.
7 changes: 2 additions & 5 deletions en/00_Getting_Started/00_Server_Requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ the server to update templates, website logic, and perform upgrades or maintenan

## PHP

- PHP >=8.1, <=8.3
- PHP 8.3
- PHP extensions: `ctype`, `dom`, `fileinfo`, `hash`, `intl`, `mbstring`, `session`, `simplexml`, `tokenizer`, `xml`
- PHP configuration: `memory_limit` with at least `48M`
- PHP extension for image manipulation: Either `gd` or `imagick`
Expand Down Expand Up @@ -295,12 +295,9 @@ table may be of use:

| Silverstripe CMS Version | PHP Version |
| ------------------------ | ----------- |
| 6.0 + | 8.3 |
| 5.2 + | 8.1 - 8.3 |
| 5.0 - 5.1 | 8.1 - 8.2 |
| 4.11 + | 7.4 - 8.1 |
| 4.10 | 7.3 - 8.0 |
| 4.5 - 4.9 | 7.1 - 7.4 |
| 4.0 - 4.4 | 5.6 - 7.4 |

From Silverstripe CMS 5 onwards, the [Silverstripe CMS major release policy](/project_governance/major_release_policy#php-support-commitments) guides which PHP versions are supported by which Silverstripe CMS release.

Expand Down
4 changes: 2 additions & 2 deletions en/00_Getting_Started/02_Composer.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ file. It will appear in your project root, and by default, it will look somethin
"type": "silverstripe-recipe",
"description": "The SilverStripe Framework Installer",
"require": {
"php": "^8.1",
"php": "^8.3",
"silverstripe/recipe-plugin": "^2",
"silverstripe/vendor-plugin": "^2",
"silverstripe/recipe-cms": "~5.0.0@stable",
Expand Down Expand Up @@ -340,7 +340,7 @@ Open `composer.json`, and find the module's `require`. Then put `as (core versio
```json
{
"require": {
"php": "^8.1",
"php": "^8.3",
"silverstripe/recipe-cms": "~5.0.0@stable",
"silverstripe/framework": "dev-myproj as 5.0.0",
"silverstripe-themes/simple": "~3.2.0"
Expand Down
2 changes: 1 addition & 1 deletion en/00_Getting_Started/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ icon: rocket

## Server requirements

Silverstripe requires PHP 8.1 or newer. It runs on many webservers and databases, but is most commonly served using
Silverstripe requires PHP 8.3 or newer. It runs on many webservers and databases, but is most commonly served using
Apache and MySQL/MariaDB.

If you are setting up your own environment, you'll need to consider a few configuration settings such as URL rewriting
Expand Down
2 changes: 1 addition & 1 deletion en/12_Project_Governance/05_Major_release_policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The Silverstripe CMS release cycle is built around these assumptions:

At launch, a Silverstripe CMS major release supports all PHP versions in full support. PHP versions in limited support are not supported at launch by new Silverstripe CMS major releases.

Following the initial launch of a Silverstripe CMS major release, the development team aims to add forward compatibility for the next PHP release. e.g: Silverstripe CMS 5 at launch will support PHP 8.1 and PHP 8.2. CMS 5 should receive official support for an eventual PHP 8.3 in early 2024.
Following the initial launch of a Silverstripe CMS major release, the development team aims to add forward compatibility for the next PHP release. e.g: Silverstripe CMS 6 at launch will support PHP 8.3 and PHP 8.4. CMS 5 should receive official support for an eventual PHP 8.5 in early 2026.

Support for end-of-life PHP releases is not dropped within a Silverstripe CMS major release line, unless it's necessary to address vulnerabilities or high impact bugs.

Expand Down

0 comments on commit 676142e

Please sign in to comment.