Conversation
Update the WordPress test environment and remove the Site Health failure that no longer occurs.
WordPress 6.8 changed get_calendar() to generate date bounds with integer month components, producing literals such as '2026-2-01'. MySQL treats those values as dates, while SQLite compares the stored values as text. Normalize non-padded temporal components so calendar queries continue to work after moving the test environment from WordPress 6.7.2 to 7.0.1.
Match MySQL affected-row semantics when a deterministic filtered UPDATE leaves stored values unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mark the SQLite plugin as tested up to WordPress 7.0, and:
Why
Make sure the SQLite plugin is tested up to WordPress 7.0.
Normalize date literals generated by WordPress 6.8 and later. WordPress 6.8 changed
get_calendar()to generate date bounds with integer month components, producing literals such as2026-2-01. MySQL interprets these values as dates, while SQLite compares temporal strings lexically. Normalizing the components preserves correct calendar queries.Verification
CI passing with tests updated to use WordPress 7.0.