-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netlify's version of this package is outdated (still on 1.0.4) #15
Comments
Thanks for reporting! |
This is the related PR in netlify/plugins repo netlify/plugins#151 |
Thanks a lot! 🙏 |
🎉 Netlify now has 1.0.8. Issue should be able to be closed. |
since netlify already merged the version upgrade PR, this issue may be considered as done ,although I noticed the recent runs for my projects still uses v1.0.4. @ehmicky would you mind help clarify when would the new version take effect in production for all projects that did not add the plugin to their devDependencies? |
Hi @bencao! |
In my
package.json
, I have the latest version of this plugin installed, which is v1.0.5:And everything was working fine on my deploy previews. But as soon as I tried a production deploy, the build failed because I'm using the
![image](https://user-images.githubusercontent.com/2475919/95694083-05b0be80-0bfe-11eb-9240-9b511fd1db1a.png)
buildEvent
input, which was added in v1.0.5, but for some reason Netlify is using v1.0.4:My guess is that since I do not have this plugin as a production dependency, Netlify is falling back to whatever version is in it's own plugin repository, and I'm guessing that version is out of date.
My current workaround has been to make this a production dependency, which allows it to take precedence over whatever is in Netlify's repository, and works:
![image](https://user-images.githubusercontent.com/2475919/95694410-e61a9580-0bff-11eb-992c-4092cb011aca.png)
The text was updated successfully, but these errors were encountered: