Repository navigation
Record why the timezone regression suite is not needed [ignore_release] - #206
Merged
Merged
Conversation
lachiebol
approved these changes
Sep 30, 2026
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
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.
Description
Plugins CI now checks whether a plugin with date or site-timezone logic runs the timezone regression suite (matomo-org/plugin-ci-workflows#22). This plugin's date references cannot produce a wrong site day, so the Plugins CI call records the reason instead of adding a suite, which clears the new coverage warning: Generated visits go through the tracker, which invalidates the site-local day of each visit, so each generator also invalidating the UTC date is only an extra; the direct-to-database generator stores UTC timestamps and invalidates nothing.
No runtime change, so no version bump or changelog entry.
Issue No
Related to matomo-org/plugin-ci-workflows#22
Steps to Replicate the Issue
Checklist