docker-library / docker-library/wordpress

More aggressive default php updates?

Open
#959 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
2k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

We currently set the default PHP (latest and plain tags) to be one that is supported upstream, but at the same time, we could be a catalyst for pushing a PHP version out of "beta support" in WordPress. Unfortunately, I don't know of a good non-subjective line for when to swap the default PHP to one of the "beta support" PHP releases in order to help push it out of beta.

https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/

Usage of PHP 8.3 and higher is at 8.9% of all WordPress sites as of April 2025. Once this surpasses 10% and assuming no further compatibility issues are reported then it’s expected that the beta label for PHP 8.3 support will be removed in the subsequent major release of WordPress

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the issue body and the linked WordPress PHP support clarification. Determine whether an objective threshold for promoting beta-supported PHP versions can be agreed on, then identify how the WordPress image's default PHP tags are maintained. Done means the policy is decided and the affected defaults are updated consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, php, wordpress
Domain
devops, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.