We’ve got a production incident today because all of a sudden Prismic started to leak “Planned to release” type and content changes via the query API v2 and broke the production (old) version which was not expecting changes. We were working from DEV environment with the new release planning to release the CMS version along with the site version.
We worked normally for the whole day yesterday (after done the first changes) and today the new version became unduly available.
The change was in a defined release:
The last time the content was published was 19d ago:
But then, today, Prismic started to answer with 2 records (!) per “singleton types” (one for the published version and another for the yet to publish), all of them considering the new structure (the property ‘gif_banner’ is new and removed properties are already missing):
The query is a standard one:
What could be the cause, since we are following documentation and expecting to use Prismic versioning capability as stated here? https://user-guides.prismic.io/en/articles/380234-what-happens-when-you-change-your-custom-type