Skip to content

Conversation

johnbillion
Copy link
Member

@johnbillion johnbillion commented Oct 6, 2025

For the 6.7 branch:

  • Deletes unnecessary workflows
  • Trims the unit testing matrix to the highest and lowest supported version of each major PHP branch.

Trac ticket: https://core.trac.wordpress.org/ticket/64083

@johnbillion johnbillion requested a review from desrosj October 6, 2025 16:57
Copy link

github-actions bot commented Oct 6, 2025

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@johnbillion johnbillion changed the title Trim the 6.7 workflows #64083 Trim the 6.7 workflows Oct 6, 2025
@johnbillion johnbillion marked this pull request as ready for review October 6, 2025 20:07
Copy link

github-actions bot commented Oct 6, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props johnbillion. 

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link
Member

@desrosj desrosj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few small suggestions. But supportive of this idea.

# Test highest and lowest supported version of each major.
php: [ '7.2', '7.4', '8.0', '8.4' ]
db-type: [ 'mariadb' ]
db-version: [ '10.4', '10.6', '10.11', '11.2' ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
db-version: [ '10.4', '10.6', '10.11', '11.2' ]
db-version: [ '10.6', '10.11' ]

11.2 was a rolling innovation release that is no longer supported. Since those releases have a short life-cycle, I lean towards saying that innovation/rolling releases are not included in test strategies for any non-supported branch.

I've also removed 10.4 here. I've opened #10166 to remove this version from trunk because usage across all WordPress sites has dropped below 1%.

- os: ubuntu-latest
php: '7.4'
db-type: 'mariadb'
db-version: '11.2'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
db-version: '10.11'

If there's agreement on the point about dropping innovation/rolling releases, these includes should be changed to the newest LTS version supported in that version.

- os: ubuntu-latest
php: '7.4'
db-type: 'mariadb'
db-version: '11.2'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
db-version: '10.11'

Same as above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants