-
Notifications
You must be signed in to change notification settings - Fork 34
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
[0.9.0] setup issue #101
Comments
Yes, it's almost certainly due to our recent change to Node 18 from Node 14. We're in the process of converting integrations over to Node 18, so some of them like Azure might require that you manually switch to Node 14 with nvm or another version management system before the execution will work. We should hopefully be getting it updated soon, but in the meantime manually switching down to 14 should hopefully be a decent workaround for you. |
In CI with starbase 0.9.0 and multiple integrations, I'm getting many unmet dependencies. https://github.com/juju4/ansible-starbase/actions/runs/5912604729/job/16036179158#step:10:21054
|
I'm working on an ansible role to setup starbase and CI test is failing since Aug 2nd. Previous execution on Jul 26th was successful.
https://github.com/juju4/ansible-starbase/actions/runs/5745725710/job/15574145225#step:7:726
https://github.com/juju4/ansible-starbase/actions/runs/5841947117/job/15842577988#step:7:613
Per https://github.com/JupiterOne/sdk/tags, latest is 9.9.3/9.11.2
Last successful action on https://github.com/JupiterOne/starbase/actions is on Jul 19th.
Maybe just need engine 14 to 18 in https://github.com/JupiterOne/starbase/blob/main/package.json#L17 ?
The text was updated successfully, but these errors were encountered: