gatsby
5.16.1 · 10 Feb 2026MIT252.9k / weekRepositoryHomepagenpmAtom feed
Upgrading gatsby from 0.12.39 to 0.12.48
9 releases in betweennotes for 4
Reading releases, release notes and advisories…
- ?
- changes to make
- 0
- advisories fixed
- ?
- new
- ?
- fixes
Counted from 4 of 9 release notes. Advisories are counted from the advisory database, in full.
Security
1 advisory still affects 0.12.48
- Gatsby develop server has Local File Inclusion vulnerabilitymoderate · GHSA-c6f8-8r25-c4gc
Upgrading to 4.25.7 clears it.
6 other lines we could not sort, mostly version bumps
- 0.12.45
@0x80 noticed that source maps weren't working in Chrome in development and asked about it. That, combined with a serendipitous tweet by @gaearon, led to #812 where we swapped out using the
evalsource-maps technique forcheap-module-source-maps. - 0.12.45
@donysukardi got us React 16 ready by removing our uses of React.createClass and the built-in proptypes #809
- 0.12.45
@danperkins fixed a logic bug in our router generation where nested templates weren't being tied to their parent templates correctly #808
- 0.12.45
@kyleamathews replaced the old default starter with a much simpler one to make it simpler to understand Gatsby when new plus easier to use the starter as a base for building new sites #806
- 0.12.40
@donysukardi added support for using Yarn over NPM when creating a new Gatsby site using
gatsby new#782 - 0.12.40
@Tom-Bonnike extended our JavaScript frontmatter code to support array values. #784 So now the parsing code can extract values in this form: