-
Notifications
You must be signed in to change notification settings - Fork 430
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
fix(cli): remove v2 commands #5750
base: next
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
abf237c
to
dd01005
Compare
No changes to documentation |
Component Testing Report Updated Apr 11, 2024 6:08 AM (UTC)
|
I personally feel this should wait until v2 EOL, as I do not see the immediate urgency in this, and it is easier to communicate. |
dd01005
to
cc4540b
Compare
- remove sanity uninstall command (v2 only) - remove sanity init plugin command (v2 only)
cc4540b
to
ca6550e
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Description
Note: I originally did this as part of the work in #5533 to get rid of yarn references + old cruft, but figured it was better to consider it in a separate PR, as I'm not entirely sure whether now is the right time.
It's a "nice-to-have" cleanup and not super important and definitely not urgent.
Removes a few v2-only commands from the CLI
sanity uninstall
sanity init plugin
sanity init
to reconfigure a v2 projectsanity check
sanity upgrade
sanity uninstall
What to review
Testing
n/a
Notes for release