Skip to content

Conversation

@jspellman814
Copy link

Addresses #399.

@jspellman814 jspellman814 requested review from a team as code owners May 1, 2023 20:39
@jspellman814 jspellman814 marked this pull request as ready for review May 3, 2023 14:13
@pwtyler
Copy link
Member

pwtyler commented May 4, 2023

@jspellman814 this closes #366 as well, correct?

Copy link
Member

@pwtyler pwtyler left a comment

Choose a reason for hiding this comment

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

LGTM once tests included.

@jspellman814 jspellman814 requested a review from pwtyler May 5, 2023 22:39
Copy link
Member

@pwtyler pwtyler left a comment

Choose a reason for hiding this comment

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

LGTM.

@jspellman814, I bumped the minor version number per the new policy in CONTRIBUTING.md, please make sure I caught all instances and you're onboard with the change.

Makes me think perhaps we should use the same in the changelog headings as well (instead of ### Latest ###), but that's a conversation for elsewhere.

@jspellman814 jspellman814 requested review from a team and pwtyler May 8, 2023 14:03
@jspellman814 jspellman814 merged commit 009f716 into develop May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

As of WordPress 6.1 A Notice About Incorrect Support for wp_cache_flush_runtime Implement wp_cache_flush_group

3 participants