You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm so sorry that this happened, this is a decision that was made before the project was forked and something we probably should have scrutinized much earlier
The reason this cleanup is in place is to prevent node installations from accumulating and filling up the disk, so while the functionality is probably not going away we absolutely should check that we're only deleting node
This has been fixed in 7.0.2, we now only delete files that either start with node-v or are in a folder starting with node-v
It's not foolproof but should help prevent worst-case scenarios
* 7.x:
7.1.0
Add license to POM #319
Update CHANGELOG
Support for AIX OS on ppc64
Drop incorrect node_modules input from documentation and tests
Remove incorrect node_modules input in pnpm test fixture
Add support for ARM64 Windows #315
Update documentation
NodeSetupTask should not delete general files, only old node versions #297
Please DO NOT DELETE everything in any directory, no matter what configuration/misconfiguration is in build.gradle file. Here is what I had in my build.gradle when this DISASTER happened π©.
After I ran gradle clean build, this is what I have in my-ui directory
drwxr-xr-x@ 9 loki staff 288 Dec 24 22:24 node-v20.10.0-darwin-x64
The text was updated successfully, but these errors were encountered: