Testing edition of a page on netlify cms, automatic deploy on Netlify fails

# Bug report

**What is the current behavior?**
I edited page on netlify cms

**If the current behavior is a bug, please provide the steps to reproduce.**
Edit a page on netlify cms

**What is the expected behavior?**
Automatic deploy should not fail after page edition

**Other relevant information:**
```
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "featuredimage" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "featuredimage". If you didn't expect "featuredimage" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "image" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "image". If you didn't expect "image" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "image" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "image". If you didn't expect "image" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "image" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "image". If you didn't expect "image" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "image" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "image". If you didn't expect "image" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "image" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "image". If you didn't expect "image" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: error There was an error in your GraphQL query:
10:02:51 AM: Field "full_image" must not have a selection since type "String" has no subfields.
10:02:51 AM: This can happen if you e.g. accidentally added { } to the field "full_image". If you didn't expect "full_image" to be of type "String" make sure that your input source and/or plugin is correct.
However, if you expect "value" to exist, the field might be accessible in another subfield. Please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have.
10:02:51 AM: It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned
"dummy content". Visit our docs to learn how you can define the schema for "undefined":
10:02:51 AM: https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
10:02:51 AM: failed extract queries from components - 0.906s
10:02:51 AM: npm ERR! code ELIFECYCLE
10:02:51 AM: npm ERR! errno 1
10:02:51 AM: npm ERR! gatsby-starter-netlify-cms@1.1.3 build: `npm run clean && gatsby build`
10:02:51 AM: npm ERR! Exit status 1
10:02:51 AM: npm ERR!
10:02:51 AM: npm ERR! Failed at the gatsby-starter-netlify-cms@1.1.3 build script.
10:02:51 AM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
10:02:51 AM: npm ERR! A complete log of this run can be found in:
10:02:51 AM: npm ERR! /opt/buildhome/.npm/_logs/2021-10-16T08_02_51_198Z-debug.log
10:02:51 AM:
```

Node.js version:
NPM/Yarn version
Operating System:
Additional tools: