Packages

gatsby

5.16.1 · 10 Feb 2026MIT252.9k / weekRepositoryHomepagenpmAtom feed

Upgrading gatsby from 0.10.0 to 0.12.48

56 releases in betweennotes for 28

Reading releases, release notes and advisories…

Other targets from 0.10.0Clears its advisory4.25.7Latest5.16.1
8+
changes to make
0
advisories fixed
7+
new
2+
fixes

Counted from 28 of 56 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • breaking0.11.0
  • breaking0.11.0
  • breaking0.11.0
  • breaking0.11.0
  • breaking0.11.0
  • breaking0.11.0
  • breaking0.11.0
  • breaking0.11.0

Security

1 advisory still affects 0.12.48

Upgrading to 4.25.7 clears it.

Release by release

  1. 0.12.13 – 0.12.4834 releases, nothing new or fixed; 17 without a note

  2. 0.12.12

    27 Sep 20162 new · 2 fixes

  3. 0.12.0 – 0.12.1111 releases, nothing new or fixed; 7 without a note

  4. 0.11.7

    6 Jul 20165 new
    • new

      @jakubrohleder added support for CSS Modules, a very long-standing request. Thanks Jakub! CSS Module support is enabled for all files with .module.(css|less|scss|sass) extension. #295

    • new

      Some css module types (Less/Sass) weren't being minimized 0a667e0

    • new

      @adjohnson916 noticed we were using a private API of React Router #343

    • new

      Added check for processes listening to the port requested by gatsby serve-build similar to what we do for gatsby listen #345

    • new

      Set the NODE_ENV to production for node code (we were already doing this for Webpack modules but some Webpack loaders don't behave correctly without this fix #348

  5. 0.10.1 – 0.11.69 releases, nothing new or fixed; 4 without a note

23 other lines we could not sort, mostly version bumps

  • @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 eval source-maps technique for cheap-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.45

  • @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:

    0.12.40

  • @ahonn noticed we were doing a full clone of Gatsby starters when running gatsby new which is wasteful as we just throw away the git repo. So in #730 he fixed that to just do a shallow clone.

    0.12.39

  • @dbismut fixed the default markdown loader to add in a site's prefix/basename to links within markdown. #710

    0.12.39

  • @mtt87 needed to support rendering translations correctly for his site during the static HTML build so added support for SSR APIs through a new gatsby-ssr.js file which can be added to your site similar to gatsby-browser.js and gatsby-node.js. He added a wrapRootComponent API similar to what was recently added to the browser but the method is now available if we need to add additional SSR APIs.

    0.12.37

  • @mjesuele added support for extracting data from JS frontmatter when using template literal strings in additional to normal strings

    0.12.37

12 internal lines (docs, tests, tooling) left out.