Some users who deployed Umami on Netlify started to have issues about responses being cached incorrectly (reference removed)

Here are a few queries which are returning the same cached response: (a part of 8 queries sent at the same moment)

/api/websites/[uuid]/metrics?startAt=1744092000000&endAt=1744178399999&unit=hour&timezone=Europe%2FParis&type=url&limit=10&search=
/api/websites/[uuid]/metrics?startAt=1744092000000&endAt=1744178399999&unit=hour&timezone=Europe%2FParis&type=referrer&limit=10&search=
/api/websites/[uuid]/metrics?startAt=1744092000000&endAt=1744178399999&unit=hour&timezone=Europe%2FParis&type=browser&limit=10&search=

Reading Netflify docs (https://docs.netlify.com/platform/caching/) and looking at the time the issue was first raised,
I wonder if this change could be the culprit: reference removed

In my understanding, having a Netlify-Vary with query=__nextDataReq is like saying that other query parameters don't affect the response, which is not the case, and all of the above queries end up in the same cache key whereas they shouldn't.
It looks like your docs example with Netlify-Vary: query=style|season.

Do I miss something?