v4.6 Release Notes
firstname.lastname@example.org release (January 2022 #2)
Key highlights of this release:
- Speeding Up Subsequent Queries
- Tracking Image Changes in Markdown Files
- New Major Version for
Also check out notable bugfixes.
Bleeding Edge: Want to try new features as soon as possible? Install
gatsby@next and let us know
if you have any issues.
Subsequent queries now get a ~10-15% performance boost! You’ll see this improvement after your first
gatsby build for all following runs (unless the cache is cleared). These percentage may defer depending on the complexity of nodes. We were able to achieve this by caching
trackedRootNodes across instances of
graphqlRunner via PR #33695
When using an image inside markdown files together with
![alt text](./some-image.jpg)) there were cases when a change to the image wasn’t reflected in the site. Changes like resizing or directly editing the image required a
gatsby clean in the past. This broken functionality is now fixed with PR #34433 and changed images will now directly show during
gatsby develop and
You can configure plugin options for your plugins and unit test the options schema using helper functions from
gatsby-plugin-utils. The schema validation for the options schema now does not throw errors anymore on warnings like unknown keys (see PR that implemented this for more information). This fixed an issue where default values where not passed through to the plugin if e.g. unknown keys were used.
Here’s a short list of changes you’ll need to make or be aware of:
pluginOptionsSchemareturns warnings instead of errors now for unknown keys
hasWarningsin addition to the existing values
- Default options you set in your plugin option schema are now correctly passed through to the plugin, even when a user sets unknown keys
Here’s a short before/after example on how to migrate your test when you’re checking for unknown keys.
gatsby-plugin-manifest: Generate icons sequentially, via PR #34331
create-gatsby: Fixed an issue where user-provided
GATSBY_TELEMETRY_DISABLEDenvironment variable did not disable telemetry, via PR #34495
gatsby-sharp: Create more resilient wrapper around sharp, via PR #34339
gatsby-source-contentful: Enable tag support for assets, via PR #34480
gatsby: Optimized queries that filter just on
id, via PR #34520
A big Thank You to our community who contributed to this release 💜