Merge release/3.0.0 additions into trunk to unblock#1113
Conversation
Co-authored-by: Mukesh Panchal <[email protected]>
Add support for autoloading enhancements in WordPress 6.6 trunk to autoloaded options Site Health check
…s are explicitly recommended, some are experimental).
Co-authored-by: Weston Ruter <[email protected]>
…annotations Implement support for annotating certain plugins as experimental
felixarntz
added
[Type] Enhancement
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
joemcgill
left a comment
joemcgill
left a comment
There was a problem hiding this comment.
This seems fine to me, though we'll need to make sure that the version bumps that get made to update the @since values also get merged back to trunk after the release. This should happen automatically if the release steps in the handbook are followed, but want to make sure we're keeping an eye on it.
github-actions
bot
temporarily deployed
to
wp.org plugin: speculation-rules
github-actions
bot
temporarily deployed
to
wp.org plugin: speculation-rules
3 participants
This is simply a merge of #1111 and #1112 from the 3.0.0 release branch into
trunk.Normally we would only do this after the 3.0.0 release, but because #1112 avoids CI failures in
trunkand #1111 unblocks working on #1032, it makes sense to already merge these two changes back at this point.