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
Several Node tools fail to install in our CI. The reason is that the failing tools have a dependency on our nodejs.vm package, that fails to install because nodejs.vm has a dependency of git with no upper bound: and that means it is installing the latest version of git that is in chocolatey, which is 2.47.1. The GitHub runners we use were updated to using this version of git on December 4th: actions/runner-images@d868709. Since then an error occurs when our packages try to install, because it fails to install git since that version is already installed. But I think the tools still get installed because of chocolatey/choco#3487 (it is supposed to be a bug, but it is a feature in this case 🤣).
@emtuls had proposed to ping an older version to fix it in the CI, but this may not fix it for all users that may have another version install.
But I all other fixes I can come up with are much more complicated to implement. As FLARE-VM/Commando-VM are recommended to be installed in an empty VM, unless someone has a better idea, I would go with @emtuls proposal. @mandiant/vms any better ideas?
The text was updated successfully, but these errors were encountered:
Details
Several Node tools fail to install in our CI. The reason is that the failing tools have a dependency on our
nodejs.vm
package, that fails to install becausenodejs.vm
has a dependency ofgit
with no upper bound: and that means it is installing the latest version of git that is in chocolatey, which is2.47.1
. The GitHub runners we use were updated to using this version of git on December 4th: actions/runner-images@d868709. Since then an error occurs when our packages try to install, because it fails to install git since that version is already installed. But I think the tools still get installed because of chocolatey/choco#3487 (it is supposed to be a bug, but it is a feature in this case 🤣).@emtuls had proposed to ping an older version to fix it in the CI, but this may not fix it for all users that may have another version install.
But I all other fixes I can come up with are much more complicated to implement. As FLARE-VM/Commando-VM are recommended to be installed in an empty VM, unless someone has a better idea, I would go with @emtuls proposal. @mandiant/vms any better ideas?
The text was updated successfully, but these errors were encountered: