Gatsby Framework Version Support
Introduction
This page illustrates the support plans for the major versions of Gatsby. This allows you to effectively plan your Gatsby framework upgrades.
Generally, you can expect 1 major version per calendar year. Although, there may be more than 1 major per year when a necessary evolution of Gatsby requires significant breaking change.
Release and support schedule
Note: Future time ranges are listed when a specific target date is not yet determined.
| Version | Status | As Of | Until |
|---|---|---|---|
| 4 | Active Long-term support | October 21, 2021 | Q4 2022 |
| 3 | Maintenance Long-term support | October 21, 2021 | Q4 2022 |
| 2 | Unsupported | January 1, 2022 | - |
Terminology
Critical Patch - A critical patch addresses an issue that prevents the Gatsby framework from delivering intended user value under typical conditions. Other items, such as minor bug fixes and new features are not considered “critical patches” to Gatsby.
Active Long-Term Support - Receives priority attention from the core maintainers of Gatsby. New features to Gatsby are only available in the Active Long-Term Supported version.
Maintenance Long-term Support - Receives critical patches, but does not receive new features.
Unsupported - This version of Gatsby no longer receives official support of any kind.
What does this mean for users of the Gatsby framework?
- To receive the newest enhancements and bug fixes, ensure that you’ve migrated to Gatsby Version 4
- Continue reporting any issues as you typically would, either using support on Gatsbyjs.com, or by opening an issues in our GitHub repository.
What does this mean for Gatsby Cloud?
Your Gatsby-powered sites will continue to run as they do today in Gatsby Cloud. However, as enhancements are delivered within Gatsby Cloud and the Gatsby framework, you may need to upgrade your site(s) in order to take advantage of those features and performance enhancements.