Skip to content

Adjust cached client fixtures for device-detector 6.5.2 [no_release] - #99

Merged
sgiehl merged 1 commit into
6.x-devfrom
composer-update
Oct 21, 2026
Merged

sgiehl merged 1 commit into
6.x-devfrom
composer-update

Conversation

@sgiehl

@sgiehl sgiehl commented Oct 20, 2026

Copy link
Copy Markdown
Member

Description

Test update for matomo-org/matomo#25548, which updates matomo/device-detector from 6.5.1 to 6.5.2.

In 6.5.2, Browser::parse() reads the engine key from the user-agent result when client hints are present. CachedBrowserParser returns the cached client as that result, but the fixtures in DeviceDetectorCacheFactoryTest and CachedEntryTest used cached clients without an engine, so both tests failed with Undefined array key "engine". Real cache entries always contain it, because writeToCache() stores getClient().

The fixtures now include the engine. Since 6.5.2 also takes the engine from client hints, the expected client is now Blink / 98.0, the same as uncached detection returns for that user agent and those client hints.

Only tests change; there is no code change in this plugin. plugins/DeviceDetectorCache in the core PR points at this branch.

Checklist

  • [✔] I have understood, reviewed, and tested all AI outputs before use
  • [✔] All AI instructions respect security, IP, and privacy rules

@sgiehl
sgiehl requested a review from a team October 21, 2026 06:52
Cached browser results always contain the engine, and client hints now provide the engine as well.
@sgiehl
sgiehl merged commit c4df910 into 6.x-dev Oct 21, 2026
22 checks passed
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.

2 participants