Make WordPress Core

Opened 7 weeks ago

Last modified 4 hours ago

#64069 new task (blessed)

Bump default theme versions for WordPress 6.9

Reported by: sabernhardt's profile sabernhardt Owned by:
Milestone: 6.9 Priority: normal
Severity: normal Version:
Component: Bundled Theme Keywords: has-patch commit 2nd-opinion
Focuses: Cc:

Description

Bundled themes will need a version bump for the 6.9 release.

Previously:
#63681 - 6.8.2
#62990 - 6.8
#62034 - 6.7
#60701 - 6.6
#59816 - 6.5
#58832 - 6.4
#57857 - 6.3
#57689 - 6.2
#56450 - 6.1
#55754 - 6.0
#54783 - 5.9
#53277 - 5.8
#52704 - 5.7
#51919 - 5.6
#50889 - 5.5
#49743 - 5.4

Change History (14)

#1 @sabernhardt
7 weeks ago

Except for Twenty Twenty-Three, all of the themes have at least one change (as of today).

#2 @sabernhardt
3 weeks ago

#63709 was marked as a duplicate.

This ticket was mentioned in PR #10493 on WordPress/wordpress-develop by @shailu25.


2 weeks ago
#3

  • Keywords has-patch added

Twenty Ten: 4.5
Twenty Eleven: 5.0
Twenty Twelve: 4.7
Twenty Thirteen: 4.5
Twenty Fourteen: 4.4
Twenty Fifteen: 4.1
Twenty Sixteen: 3.7
Twenty Seventeen: 4.0
Twenty Nineteen: 3.2
Twenty Twenty: 3.0
Twenty Twenty-One: 2.7
Twenty Twenty-Two: 2.1
Twenty Twenty-Three: 1.7
Twenty Twenty-Four: 1.4
Twenty Twenty-Five: 1.4

Trac ticket: #60999

@sabernhardt commented on PR #10493:


13 days ago
#4

I'm not ready to do a thorough review, but I have two comments.

  • r60934 added package.json and package-lock.json files to Twenty Twenty-Two and Twenty Twenty-Five, and those also need updates to the version number.
  • Twenty Twenty-Three still has no code changes since 1.6. That theme might only have the "Tested up to" version bump, as in r60158, again without packaging a new theme.

@shailu25 commented on PR #10493:


13 days ago
#5

All the mentioned feedback has been incorporated in the latest commit.

This ticket was mentioned in Slack in #core by welcher. View the logs.


11 days ago

@wildworks commented on PR #10493:


10 days ago
#7

https://github.com/WordPress/wordpress-develop/blob/a44019b4084cf1f20c97189020942383b029234c/src/wp-content/themes/twentyeleven/inc/theme-options.php#L421

The dark.css file has been updated with the following changeset:

https://core.trac.wordpress.org/changeset/60960

If we respect the commit date of the changeset, the new string will be 20251017. If we respect the 6.9 release date, it will be 20251202.

@wildworks commented on PR #10493:


10 days ago
#8

As far as my research goes, that's all the feedback I have. I would appreciate it if someone more knowledgeable could add further reviews.

@shailu25 commented on PR #10493:


10 days ago
#9

https://github.com/WordPress/wordpress-develop/blob/a44019b4084cf1f20c97189020942383b029234c/src/wp-content/themes/twentyeleven/inc/theme-options.php#L421

The dark.css file has been updated with the following changeset:

https://core.trac.wordpress.org/changeset/60960

If we respect the commit date of the changeset, the new string will be 20251017. If we respect the 6.9 release date, it will be 20251202.

I agree this date should be last modified date. I will update this date.

@wildworks commented on PR #10493:


10 days ago
#10

@shail-mehta, The force push may have caused a regression 😅

Released: December 02, 2025 should be Released: December 2, 2025

@shailu25 commented on PR #10493:


10 days ago
#11

Yeah I reverting it

This ticket was mentioned in Slack in #core by wildworks. View the logs.


4 days ago

#13 @wildworks
4 days ago

  • Keywords commit 2nd-opinion added

This ticket was brought up in the 6.9 Bug SCrub today. From what I can see, it's ready to commit, but I'd appreciate some second feedback from someone more knowledgeable.

@umeshsinghin commented on PR #10493:


4 hours ago
#14

I’ve gone through the PR, and it looks all set from my side.

Note: See TracTickets for help on using tickets.