Static query not invalidating hash

Looking at the guidance on caching (https://www.gatsbyjs.org/docs/caching/#static-files) I think the recent changes to static queries isn’t correct with this. @sidharthachatterjee I don’t know if this is something you can answer?

The guidance is:

All files in static/ should be cached forever

However the .json files that are output to the static/d folder look like a hash of the query (schema?) and not of the query result. Images are requested like /icons/icon-512x512.png?v=6097298229b47b2e2010b1492c6fee40, where the v seems to be a hash of something that rotates when an image has changed.

Is this ?v= supposed to be applied to the static/d/<hash>.json files as well?

Steps to recreate

1. Create gatsby-starter-default
2. gatsby build
3. Observe static/d/ folder
4. Change siteMetadata title, for example
5. gatsby build
6. Observe static/d/ folder, it hasn’t changed

[sidharthachatterjee]

We switch the location for static queries into public/page-data/sq/d

Fix published in gatsby@2.24.33

[danielmgzzg]

Guys, thank you so much for fixing this issue. I just wish we had found it earlier in the docs or something we have been clueless for months and tried all sort of things until we looked closely at the .json from the static queries and searched for this