Merge branch 'master' of https://github.com/redabacha/gatsby into fix…

…/gatsby-plugin-image-missing-error

.circleci/config.yml

@@ -128,22 +128,6 @@ aliases:
       - notify-status:
           condition: << parameters.nightly >>
 
-  e2e_tests_gatsby-image_alias: &e2e_tests_gatsby-image_alias
-    <<: *e2e-executor
-    parameters:
-      nightly:
-        type: boolean
-        default: false
-    environment:
-      CYPRESS_PROJECT_ID: ave32k
-      CYPRESS_RECORD_KEY: fb3cb6e0-a0f9-48b2-aa9a-95e8ef150a85
-    steps:
-      - e2e-test:
-          test_path: e2e-tests/gatsby-image
-          skip_file_change_test: << parameters.nightly >>
-      - notify-status:
-          condition: << parameters.nightly >>
-
 commands:
   notify-status:
     parameters:
@@ -379,15 +363,6 @@ jobs:
           command: 'DEBUG=start-server-and-test yarn start-server-and-test "yarn develop 2>&1 | tee log.txt" :8000 "! cat log.txt | grep -E ''ERROR #|Require stack:''"'
           working_directory: /tmp/e2e-tests/gatsby-pnp
 
-  e2e_tests_gatsby-image:
-    <<: *e2e_tests_gatsby-image_alias
-
-  e2e_tests_gatsby-image_with_experimental_react:
-    <<: *e2e_tests_gatsby-image_alias
-
-  e2e_tests_gatsby-image_with_next_react:
-    <<: *e2e_tests_gatsby-image_alias
-
   e2e_tests_development_runtime:
     <<: *e2e_tests_development_runtime_alias
 
@@ -603,10 +578,6 @@ workflows:
     jobs:
       - bootstrap-with-experimental-react:
           version: "next"
-      - e2e_tests_gatsby-image_with_next_react:
-          nightly: true
-          requires:
-            - bootstrap-with-experimental-react
       - e2e_tests_development_runtime_with_next_react:
           nightly: true
           requires:
@@ -626,10 +597,6 @@ workflows:
     jobs:
       - bootstrap-with-experimental-react:
           version: "experimental"
-      - e2e_tests_gatsby-image_with_experimental_react:
-          nightly: true
-          requires:
-            - bootstrap-with-experimental-react
       - e2e_tests_development_runtime_with_experimental_react:
           nightly: true
           requires:
@@ -697,8 +664,6 @@ workflows:
           <<: *e2e-test-workflow
       - e2e_tests_path-prefix:
           <<: *e2e-test-workflow
-      - e2e_tests_gatsby-image:
-          <<: *e2e-test-workflow
       - e2e_tests_gatsby-static-image:
           <<: *e2e-test-workflow
       - e2e_tests_visual-regression:

.eslintignore

@@ -22,7 +22,6 @@ integration-tests
 packages/*/*.js
 packages/gatsby-source-shopify/**/*.js
 packages/gatsby-plugin-preload-fonts/prepare/*.js
-packages/gatsby-image/withIEPolyfill/index.js
 packages/gatsby/cache-dir/commonjs/**/*
 packages/gatsby-admin/public
 packages/gatsby/gatsby-admin-public

.eslintrc.js

@@ -36,6 +36,7 @@ module.exports = {
     __PATH_PREFIX__: true,
     __BASE_PATH__: true,
     __ASSET_PREFIX__: true,
+    _CFLAGS_: true,
   },
   rules: {
     "@babel/no-unused-expressions": [

.github/ISSUE_TEMPLATE/BUG_REPORT.yml

@@ -11,6 +11,7 @@ body:
         Please fill out each section below. This info allows Gatsby maintainers to diagnose (and fix!) your issue as quickly as possible. Otherwise we might need to close the issue without e.g. clear reproduction steps.
 
         Also please verify that your issue is present in `gatsby@next`, too. The `next` version is the latest beta version of Gatsby and has any pending changes that are in the next stable release.
+        Bug reports also shoulnd't be used for support requests about a specific problem in your site, please use GitHub Discussions for that.
 
         Useful Links:
         - Documentation: https://www.gatsbyjs.com/docs/
@@ -22,7 +23,7 @@ body:
       options:
         - label: "This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues"
           required: true
-        - label: "This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions"
+        - label: "This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions"
           required: true
   - type: textarea
     attributes:
@@ -36,7 +37,7 @@ body:
     attributes:
       label: Reproduction Link
       placeholder: "https://github.com/username/repository-name/"
-      description: "Link to a reproduction (GitHub repository, Codesandbox, etc.). How to make a minimal reproduction: https://gatsby.dev/reproduction"
+      description: "Link to a reproduction (GitHub repository, Codesandbox, etc.). **Do not link to your actual project**, but provide a minimal reproduction in a fresh project -- how to make a minimal reproduction: https://gatsby.dev/reproduction"
     validations:
       required: true
   - type: textarea

SECURITY.md

@@ -13,4 +13,8 @@ The following versions are currently being supported with security updates.
 
 ## Reporting a Vulnerability
 
-Please email security@gatsbyjs.com
+If you believe you have found a security issue with any of Gatsby's open source or commercial offerings, we would love to receive your report! Security findings can be emailed to security@gatsbyjs.com.
+
+When reporting a security issue, describe the issue in detail and include steps to reproduce. The more detail provided, the more likely we will be able to reproduce the issue and determine a course of action.
+
+Please do not report findings from `npm audit`. We are aware of package dependency issues that are reported by this tool and do review these reports. In many cases the issues reported by `npm audit` are misleading and do not present a tangible/exploitable security risk for Gatsby users.

benchmarks/query-filters-sort/gatsby-config.js

@@ -4,5 +4,8 @@ module.exports = {
     description: `The filters and sort benchmark`,
     author: `@gatsbyjs`,
   },
+  flags: {
+    PARALLEL_QUERY_RUNNING: true,
+  }
   // plugins: [`gatsby-plugin-benchmark-reporting`],
 }

benchmarks/query-filters-sort/package.json

@@ -9,7 +9,8 @@
     "serve": "gatsby serve"
   },
   "dependencies": {
-    "gatsby": "^3.4.1",
+    "gatsby": "next",
+    "lmdb-store": "^1.6.1",
     "process-top": "^1.2.0",
     "react": "^17.0.2",
     "react-dom": "^17.0.2",

packages/gatsby-image/CHANGELOG.md → deprecated-packages/gatsby-image/CHANGELOG.md

@@ -3,6 +3,14 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.12.0-next.0](https://github.com/gatsbyjs/gatsby/compare/gatsby-image@3.11.0-next.0...gatsby-image@3.12.0-next.0) (2021-07-29)
+
+**Note:** Version bump only for package gatsby-image
+
+# [3.11.0-next.0](https://github.com/gatsbyjs/gatsby/compare/gatsby-image@3.10.0-next.1...gatsby-image@3.11.0-next.0) (2021-07-15)
+
+**Note:** Version bump only for package gatsby-image
+
 # [3.10.0-next.1](https://github.com/gatsbyjs/gatsby/compare/gatsby-image@3.10.0-next.0...gatsby-image@3.10.0-next.1) (2021-07-08)
 
 **Note:** Version bump only for package gatsby-image

packages/gatsby-image/README.md → deprecated-packages/gatsby-image/README.md

@@ -400,7 +400,7 @@ While you could achieve a similar effect with plain CSS media queries, `gatsby-i
 | `fluid`                | `object` / `array`  | Data returned from the `fluid` query. When prop is an array it has to be combined with `media` keys, allows for art directing `fluid` images. |
 | `fadeIn`               | `bool`              | Defaults to fading in the image on load                                                                                                       |
 | `durationFadeIn`       | `number`            | fading duration is set up to 500ms by default                                                                                                 |
-| `title`                | `string`            | Passed to the `img` element                                                                                                                   |  |
+| `title`                | `string`            | Passed to the `img` element                                                                                                                   |
 | `alt`                  | `string`            | Passed to the `img` element. Defaults to an empty string `alt=""`                                                                             |
 | `crossOrigin`          | `string`            | Passed to the `img` element                                                                                                                   |
 | `className`            | `string` / `object` | Passed to the wrapper element. Object is needed to support Glamor's css prop                                                                  |

packages/gatsby-image/package.json → deprecated-packages/gatsby-image/package.json

@@ -1,21 +1,21 @@
 {
   "name": "gatsby-image",
   "description": "Lazy-loading React image component with optional support for the blur-up effect.",
-  "version": "3.10.0-next.1",
+  "version": "3.12.0-next.0",
   "author": "Kyle Mathews <mathews.kyle@gmail.com>",
   "bugs": {
     "url": "https://github.com/gatsbyjs/gatsby/issues"
   },
   "dependencies": {
-    "@babel/runtime": "^7.14.6",
+    "@babel/runtime": "^7.14.8",
     "object-fit-images": "^3.2.4",
     "prop-types": "^15.7.2"
   },
   "devDependencies": {
-    "@babel/cli": "^7.14.5",
-    "@babel/core": "^7.14.6",
+    "@babel/cli": "^7.14.8",
+    "@babel/core": "^7.14.8",
     "@testing-library/react": "^9.5.0",
-    "babel-preset-gatsby-package": "^1.10.0-next.1",
+    "babel-preset-gatsby-package": "^1.12.0-next.0",
     "cross-env": "^7.0.3",
     "jest-matchmedia-mock": "^1.1.0"
   },

packages/gatsby-plugin-glamor/CHANGELOG.md → deprecated-packages/gatsby-plugin-glamor/CHANGELOG.md

@@ -3,6 +3,14 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.12.0-next.0](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-glamor@3.11.0-next.0...gatsby-plugin-glamor@3.12.0-next.0) (2021-07-29)
+
+**Note:** Version bump only for package gatsby-plugin-glamor
+
+# [3.11.0-next.0](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-glamor@3.10.0-next.1...gatsby-plugin-glamor@3.11.0-next.0) (2021-07-15)
+
+**Note:** Version bump only for package gatsby-plugin-glamor
+
 # [3.10.0-next.1](https://github.com/gatsbyjs/gatsby/compare/gatsby-plugin-glamor@3.10.0-next.0...gatsby-plugin-glamor@3.10.0-next.1) (2021-07-08)
 
 **Note:** Version bump only for package gatsby-plugin-glamor

packages/gatsby-plugin-glamor/package.json → deprecated-packages/gatsby-plugin-glamor/package.json

@@ -1,20 +1,20 @@
 {
   "name": "gatsby-plugin-glamor",
   "description": "Gatsby plugin to add support for Glamor",
-  "version": "3.10.0-next.1",
+  "version": "3.12.0-next.0",
   "author": "Kyle Mathews <mathews.kyle@gmail.com>",
   "bugs": {
     "url": "https://github.com/gatsbyjs/gatsby/issues"
   },
   "dependencies": {
-    "@babel/runtime": "^7.14.6"
+    "@babel/runtime": "^7.14.8"
   },
   "devDependencies": {
-    "@babel/cli": "^7.14.5",
-    "@babel/core": "^7.14.6",
-    "babel-preset-gatsby-package": "^1.10.0-next.1",
+    "@babel/cli": "^7.14.8",
+    "@babel/core": "^7.14.8",
+    "babel-preset-gatsby-package": "^1.12.0-next.0",
     "cross-env": "^7.0.3",
-    "gatsby-plugin-utils": "^1.10.0-next.1"
+    "gatsby-plugin-utils": "^1.12.0-next.0"
   },
   "homepage": "https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-glamor#readme",
   "keywords": [

docs/contributing/community.md

@@ -32,7 +32,7 @@ The Gatsby community welcomes contributions. Please refer to the guides below on
 - [How to Open a Pull Request](/contributing/how-to-open-a-pull-request/)
 - [Make feature requests with an RFC](/blog/2018-04-06-introducing-gatsby-rfc-process/)
 - [Gatsby Style Guide](/contributing/gatsby-style-guide/)
-- [Gatsby Translations](/contributing/gatsby-docs-translation-guide/)
+- [Gatsby Translations - currently on hold](/contributing/translation/)
 
 ## Gatsby news
 

docs/contributing/translation/index.md

@@ -4,6 +4,8 @@ title: Translating the Gatsby Documentation
 
 import LangList from "@components/lang-list"
 
+> ⚠️ Note: At the moment our localization efforts are on pause, as we shifted towards a [redesign of the docs](https://www.gatsbyjs.com/blog/announcing-new-gatsby-docs-site/). Right now, we're prioritizing a new version of the tutorial. As with all prioritization efforts, we will weigh this, amongst other potential features, fixes, and improvements, and may consider picking up on the internationalization efforts of 2020. The repositories inside the GitHub org will remain. For now we archived the respective language channels on our Discord and the role for language maintainers.
+
 There is an ongoing effort to translate the content in the Gatsby docs into multiple languages. For members of the community around the world building Gatsby sites and learning about web development, having docs and learning materials in your own language provides a lot of value. There's also a great opportunity for folks like you to contribute to the translations of the Gatsby docs.
 
 If you're a fluent speaker of a language other than English and you're interested in helping translate [gatsbyjs.com](https://gatsbyjs.com), here is some information for you to know:

docs/contributing/translation/maintainers.md

@@ -2,6 +2,8 @@
 title: Translation Maintainer Guide
 ---
 
+> ⚠️ Note: At the moment our localization efforts are on pause, as we shifted towards a [redesign of the docs](https://www.gatsbyjs.com/blog/announcing-new-gatsby-docs-site/). Right now, we're prioritizing a new version of the tutorial. As with all prioritization efforts, we will weigh this, amongst other potential features, fixes, and improvements, and may consider picking up on the internationalization efforts of 2020. The repositories inside the GitHub org will remain. For now we archived the respective language channels on our Discord and the role for language maintainers.
+
 This page lists the responsibilities of translation maintainers and provides tips on how to better manage your repository.
 
 ## Maintainer responsibilities

docs/contributing/translation/new-translations.md

@@ -2,6 +2,8 @@
 title: Starting a New Translation
 ---
 
+> ⚠️ Note: At the moment our localization efforts are on pause, as we shifted towards a [redesign of the docs](https://www.gatsbyjs.com/blog/announcing-new-gatsby-docs-site/). Right now, we're prioritizing a new version of the tutorial. As with all prioritization efforts, we will weigh this, amongst other potential features, fixes, and improvements, and may consider picking up on the internationalization efforts of 2020. The repositories inside the GitHub org will remain. For now we archived the respective language channels on our Discord and the role for language maintainers.
+
 This page lists the steps to take to create a new Gatsby docs translation.
 
 ## Creating a translation

docs/contributing/translation/style-guide.md

@@ -2,6 +2,8 @@
 title: Translation Style Guide
 ---
 
+> ⚠️ Note: At the moment our localization efforts are on pause, as we shifted towards a [redesign of the docs](https://www.gatsbyjs.com/blog/announcing-new-gatsby-docs-site/). Right now, we're prioritizing a new version of the tutorial. As with all prioritization efforts, we will weigh this, amongst other potential features, fixes, and improvements, and may consider picking up on the internationalization efforts of 2020. The repositories inside the GitHub org will remain. For now we archived the respective language channels on our Discord and the role for language maintainers.
+
 Each language translation may have some specific ways it differs from the advice Gatsby provides for writing in English, such as the use of "you" as the pronoun or the Oxford comma. Each translation group should decide on conventions and stick with them for consistency, documenting those decisions in the repo's [style guide](https://github.com/gatsbyjs/gatsby-i18n-source/blob/master/style-guide.md) file to set contributors up for success. Use the [English style guide](/contributing/gatsby-style-guide/) as a reference to determine the equivalent rules in your language.
 
 Guidelines that remain firm no matter the language stem from the goals and values of Gatsby as a project: to provide a **friendly community for Gatsby learners of all skill and experience levels** that's also **safe and welcoming to contributors**. Translated docs and learning materials should [maintain these values](/blog/2019-04-19-gatsby-why-we-write/) with **high-quality spelling and grammar**, accurate information, similar structure and purpose. For any questions about guidelines, feel free to [get in touch](/contributing/how-to-contribute/#not-sure-how-to-start-contributing) with the Gatsby team.

docs/contributing/translation/sync-guide.md

@@ -2,6 +2,8 @@
 title: Keeping Translations Up-to-date
 ---
 
+> ⚠️ Note: At the moment our localization efforts are on pause, as we shifted towards a [redesign of the docs](https://www.gatsbyjs.com/blog/announcing-new-gatsby-docs-site/). Right now, we're prioritizing a new version of the tutorial. As with all prioritization efforts, we will weigh this, amongst other potential features, fixes, and improvements, and may consider picking up on the internationalization efforts of 2020. The repositories inside the GitHub org will remain. For now we archived the respective language channels on our Discord and the role for language maintainers.
+
 Every Friday at 6:00 PM PST, gatsbybot will run a sync script on every translation repo to bring them up-to-date with the current English repo. If there is an update to a page that is already translated, gatsbybot will create a pull request listing the conflicts between the translation and the new English content. Resolving these conflicts and merging these pull requests is essential to keeping your translation repo up-to-date.
 
 ## Gatsbybot sync behavior

docs/contributing/translation/translators.md

@@ -2,6 +2,8 @@
 title: Contributing to a Translation
 ---
 
+> ⚠️ Note: At the moment our localization efforts are on pause, as we shifted towards a [redesign of the docs](https://www.gatsbyjs.com/blog/announcing-new-gatsby-docs-site/). Right now, we're prioritizing a new version of the tutorial. As with all prioritization efforts, we will weigh this, amongst other potential features, fixes, and improvements, and may consider picking up on the internationalization efforts of 2020. The repositories inside the GitHub org will remain. For now we archived the respective language channels on our Discord and the role for language maintainers.
+
 Once a language repository is created and someone on the Gatsby team has assigned codeowners, contributions can begin. It is up to the discretion of the contributor how exactly they want to work, but it's recommended to limit the scope of PRs to 1 doc at a time to aid with code reviewing.
 
 > ⚠️ Note: All contributors are expected to follow the [Gatsby Code of Conduct](/contributing/code-of-conduct/) and work professionally with fellow contributors. For issues with conduct, if you are unable to work things out amicably amongst yourselves (perhaps after filing a public issue or having a discussion on Discord), you can contact the Gatsby team at [conduct@gatsbyjs.com](mailto:conduct@gatsbyjs.com) with details about the situation.

docs/docs/ab-testing.md

@@ -8,8 +8,8 @@ Traditional A/B testing tools can slow down your site, and in general don't work
 
 However, there are several potential approaches:
 
-- **Use traditional A/B testing tools** like Optimizely. This will slow down your website because the client-side Javascript used by these tools is quite heavy. In addition, you'll need to make sure to use the correct React component, since you should not be overwriting the DOM manually.
+- **Use traditional A/B testing tools** like Optimizely. This will slow down your website because the client-side JavaScript used by these tools is quite heavy. In addition, you'll need to make sure to use the correct React component, since you should not be overwriting the DOM manually.
 
-- **Use branch-based A/B testing**. For teams of developers without any content editors using a CMS, tools like [Netlify's branch-based A/B testing can work quite well with Gatsby.](./how-to/testing/ab-testing-with-google-analytics-and-netlify.md)
+- **Use branch-based A/B testing**. For teams of developers without any content editors using a CMS, tools like [Netlify's branch-based A/B testing can work quite well with Gatsby.](/docs/how-to/testing/ab-testing-with-google-analytics-and-netlify/)
 
 - **Edge-based page splitting**. Some JAMStack vendors like [Outsmartly](https://www.outsmartly.com/) and [Uniform](https://uniform.dev/) have edge CDN integrations that allow them to serve multiple versions of a page, enabling personalization and A/B testing without a performance hit.