-
Notifications
You must be signed in to change notification settings - Fork 37
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
ci: remove package.json prepare #4388
Conversation
✅ Deploy Preview for docs-spectrocloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
(cherry picked from commit 8bfcdb7)
(cherry picked from commit 8bfcdb7)
(cherry picked from commit 8bfcdb7)
(cherry picked from commit 8bfcdb7)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
(cherry picked from commit 8bfcdb7) Co-authored-by: Karl Cardenas <[email protected]>
(cherry picked from commit 8bfcdb7) Co-authored-by: Karl Cardenas <[email protected]>
(cherry picked from commit 8bfcdb7) Co-authored-by: Karl Cardenas <[email protected]>
(cherry picked from commit 8bfcdb7) Co-authored-by: Karl Cardenas <[email protected]>
🎉 This issue has been resolved in version 4.5.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Describe the Change
This PR removes a setting that needs more experimentation from Netlify. Two packages were also moved up to dependencies vs devDependencies.
axios
andp-ratelimit
is needed for the packs download. If the env variableNODE_ENV
is set toproduction
then Netlify will not install dev dependencies. That will cause issues for our pre-build steps that retrieve packs, and security bulletins [future].Backports
Can this PR be backported?