Unable to upgrade @netlify/plugin-gatsby

Support Build Plugins
1

Hi,
Whenever I build/deploy my site I get the following message:

❯ Outdated plugins
 - @netlify/plugin-gatsby@3.2.1: latest version is 3.5.1
Migration guide: https://ntl.fyi/gatsby-plugin-migration
To upgrade this plugin, please uninstall and re-install it from the Netlify plugins directory (https://app.netlify.com/plugins)

The migration guide tells me the plugin is installed automatically and doesn’t specify how to upgrade.
The second link (Netlify) takes me to a UI with some plugins but without any gatsby ones. So how do I upgrade?

2

Try referring to:

GitHub - netlify/netlify-plugin-gatsby: A build plugin to integrate Gatsby seamlessly with Netlify (specifically, file-based method).

3

Thanks for your response.
When I do that I get the following error:

   To upgrade this plugin, please remove it from "netlify.toml" and install it from the Netlify plugins directory instead (https://app.netlify.com/plugins)
4

In that case, does going to site settings > build and deploy > setting Runtime to Gatsby solve this for you?

5

Thanks for your response.
the runtime is already set to Gatsby

6

What site is this about?

7

monitorbooks.netlify.app

8

I’m having the same issue did you end up finding a solution? Thanks

9

Hi @nicodann. Unfortunately not

10

:wave: @ricojamjar , looks like the site has been renamed or deleted. Could you share the new site slug/name so that we may take a closer look? Thanks!

11

Apologies, this is the correct link

12

hi @ricojamjar and @nicodann

Try this to upgrade to the latest version:

  • remove any references to @netlify/plugin-gatsby from your package.json
  • On site settings > build and deploy > Continuous Deployment > Build Settings remove Gatsby:

image
image2318×1540 167 KB

… the on the same option, enable it again.

  • run a build without cache.

Does that help?

1 Like
13

Hi @gualter thanks for your suggestion but this doesn’t help. Any further advice?

14

Are you really intending to revive this old thread?

15

Would you prefer me to start a new one?

16

Nope, just wanted to confirm you are still chasing an issue more than a year old.

Could you confirm you’ve added the latest version to your package.json?

17

Resolved now, thanks for your help