I’m running a Gridsome (Vue based Gatsby) powered JAMstack site that uses Forestry as a CMS.
Gridsome updated their package from 0.6.7 to 0.6.8 over the weekend. At this point of time, I did not update Gridsome to 0.6.8 in my local environment.
On Monday a collaborator added a post via Forestry to the site. When Netlify caught the changes and rebuilt the site, it installed Gridsome 0.6.8 despite Gridsome in my package.json being set to use to 0.6.7.
I noticed this happening the last few times Gridsome updated, but it didn’t cause any problems until yesterday when the builds started to fail. The site would have updated without any issues if Netlify installed the same version of Gridsome specified in my package.json. I went in and updated my site to be compatible with 0.6.8, but I can’t take immediate action to every time a developer updates a package I use in my project.
Is this the way Netlify handles installing npm packages by default? Is there something I can do to ensure that the dependencies in my package.json are the same version that Netlify is installing on their end?