WordPress.org
Get WordPress

Make WordPress Core

Opened 9 months ago

Closed 8 months ago

#63595 closed task (blessed) (fixed)

Cease support for 4.1 - 4.6

Reported by: johnbillion's profile johnbillion Owned by: johnbillion's profile johnbillion
Milestone: 6.8.2 Priority: normal
Severity: normal Version:
Component: Security Keywords: has-patch
Focuses: Cc:

Description (last modified by johnbillion)

​Security support for branches 4.1 - 4.6 will cease when 6.8.2 ships in July 2025. This is the tracking ticket for changes that need to be made to trunk and the affected branches.

Change History (40)

#1 @johnbillion
9 months ago

  • Description modified (diff)

This ticket was mentioned in ​PR #9010 on ​WordPress/wordpress-develop by ​@johnbillion.
9 months ago #2

  • Keywords has-patch added

This ticket was mentioned in ​Slack in #core by zunaid321. ​View the logs.
9 months ago

​@audrasjb commented on ​PR #9037:
9 months ago #10

## Before patch

https://github.com/user-attachments/assets/532fa5e6-e127-4cc2-929e-43e23b7b94c3

## After patch

https://github.com/user-attachments/assets/003084c2-7e06-49e3-ab30-5781f9c5e187

​@audrasjb commented on ​PR #9036:
9 months ago #11

Tested on branch 4.5, works fine.

#12 @audrasjb
9 months ago

Thanks @johnbillion. PR 9032 to 9037 are tested and approved on my side.

#13 @audrasjb
9 months ago

  • Component changed from General to Security

#14 @SirLouen
9 months ago

Test Report

✅ This report validates that the indicated 6 patches work as expected.

WP 4.1 Report

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/9032.diff

WP 4.1 Environment

  • WordPress: 4.1
  • PHP: 5.6.40
  • Server: Apache/2.4.25 (Debian)
  • Database: mysqli (Server: 11.8.2-MariaDB-ubu2404 / Client: mysqlnd 5.0.11-dev)
  • Browser: Chrome 137.0.0.0
  • OS: Windows 10/11
  • Theme: Twenty Fifteen 1.0
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Patch results

✅ Patch is working as expected

https://i.imgur.com/OKYRo79.png

WP 4.2 Report

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/9033.diff

WP 4.2 Environment

  • WordPress: 4.2
  • PHP: 5.6.40
  • Server: Apache/2.4.25 (Debian)
  • Database: mysqli (Server: 11.8.2-MariaDB-ubu2404 / Client: mysqlnd 5.0.11-dev)
  • Browser: Chrome 137.0.0.0
  • OS: Windows 10/11
  • Theme: Twenty Fifteen 1.1
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Patch results

✅ Patch is working as expected

https://i.imgur.com/pgqouhB.png

WP 4.3 Report

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/9034.diff

WP 4.3 Environment

  • WordPress: 4.3
  • PHP: 5.6.40
  • Server: Apache/2.4.25 (Debian)
  • Database: mysqli (Server: 11.8.2-MariaDB-ubu2404 / Client: mysqlnd 5.0.11-dev)
  • Browser: Chrome 137.0.0.0
  • OS: Windows 10/11
  • Theme: Twenty Fifteen 1.3
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Patch results

✅ Patch is working as expected

https://i.imgur.com/EhLmxwn.png

WP 4.4 Report

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/9035.diff

WP 4.4 Environment

  • WordPress: 4.4
  • PHP: 5.6.40
  • Server: Apache/2.4.25 (Debian)
  • Database: mysqli (Server: 11.8.2-MariaDB-ubu2404 / Client: mysqlnd 5.0.11-dev)
  • Browser: Chrome 137.0.0.0
  • OS: Windows 10/11
  • Theme: Twenty Sixteen 1.0
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Patch results

✅ Patch is working as expected

https://i.imgur.com/kjjo7jF.png

WP 4.5 Report

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/9036.diff

WP 4.5 Environment

  • WordPress: 4.5
  • PHP: 5.6.40
  • Server: Apache/2.4.25 (Debian)
  • Database: mysqli (Server: 11.8.2-MariaDB-ubu2404 / Client: mysqlnd 5.0.11-dev)
  • Browser: Chrome 137.0.0.0
  • OS: Windows 10/11
  • Theme: Twenty Sixteen 1.2
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Patch results

✅ Patch is working as expected

https://i.imgur.com/7d3cPVB.png

WP 4.6 Report

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/9037.diff

WP 4.6 Environment

  • WordPress: 4.6
  • PHP: 5.6.40
  • Server: Apache/2.4.25 (Debian)
  • Database: mysqli (Server: 11.8.2-MariaDB-ubu2404 / Client: mysqlnd 5.0.11-dev)
  • Browser: Chrome 137.0.0.0
  • OS: Windows 10/11
  • Theme: Twenty Sixteen 1.3
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.0

Patch results

✅ Patch is working as expected
https://i.imgur.com/S2YXHkO.png

Version 2, edited 9 months ago by SirLouen (previous) (next) (diff)

#15 @johnbillion
9 months ago

In 60333:

Security: Replace update nag to indicate end of support for 4.1.

Replaces the update nag to indicate that users need to update to a newer version of WordPress in order to continue receiving security updates.

Props audrasjb, peterwilsoncc, SirLouen

See #63595

#16 @johnbillion
9 months ago

In 60334:

Security: Replace update nag to indicate end of support for 4.2.

Replaces the update nag to indicate that users need to update to a newer version of WordPress in order to continue receiving security updates.

Props audrasjb, peterwilsoncc, SirLouen

See #63595

#17 @johnbillion
9 months ago

In 60335:

Security: Replace update nag to indicate end of support for 4.3.

Replaces the update nag to indicate that users need to update to a newer version of WordPress in order to continue receiving security updates.

Props audrasjb, peterwilsoncc, SirLouen

See #63595

#18 @johnbillion
9 months ago

In 60336:

Security: Replace update nag to indicate end of support for 4.4.

Replaces the update nag to indicate that users need to update to a newer version of WordPress in order to continue receiving security updates.

Props audrasjb, peterwilsoncc, SirLouen

See #63595

#19 @johnbillion
9 months ago

In 60337:

Security: Replace update nag to indicate end of support for 4.5.

Replaces the update nag to indicate that users need to update to a newer version of WordPress in order to continue receiving security updates.

Props audrasjb, peterwilsoncc, SirLouen

See #63595

#20 @johnbillion
9 months ago

In 60338:

Security: Replace update nag to indicate end of support for 4.6.

Replaces the update nag to indicate that users need to update to a newer version of WordPress in order to continue receiving security updates.

Props audrasjb, peterwilsoncc, SirLouen

See #63595

#27 follow-up: @jorbin
9 months ago

I wonder if the strings that are being put in the versions that aren't going to receive support should also be in trunk and backported now. This way they are translated ahead of time similar to about page strings.

#28 @johnbillion
9 months ago

In 60341:

Security: Cease support for WordPress 4.1 through 4.6.

Props desrosj, sirlouen, johnbillion.

See #63595

#29 in reply to: ↑ 27 @johnbillion
9 months ago

Replying to jorbin:

I wonder if the strings that are being put in the versions that aren't going to receive support should also be in trunk and backported now. This way they are translated ahead of time similar to about page strings.

Those strings were introduced in #56532 and #57216, and they were all backported to 3.7 👍.

This ticket was mentioned in ​Slack in #core by audrasjb. ​View the logs.
8 months ago

#32 @audrasjb
8 months ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Well done everyone.
As per today's bug scrub and since each PR has been committed, I'm closing this as fixed.
Feel free to reopen it if anything is missing :)

#33 @audrasjb
8 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Reopening this as we still need to commit the version bump PRs.

​@audrasjb commented on ​PR #9046:
8 months ago #34

committed!

​@audrasjb commented on ​PR #9047:
8 months ago #35

committed!

​@audrasjb commented on ​PR #9048:
8 months ago #36

committed!

​@audrasjb commented on ​PR #9049:
8 months ago #37

committed!

​@audrasjb commented on ​PR #9050:
8 months ago #38

committed!

​@audrasjb commented on ​PR #9051:
8 months ago #39

committed!

#40 @audrasjb
8 months ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Closing as fixed. All the changesets were committed to the related branches.

Note: See TracTickets for help on using tickets.