-
-
Notifications
You must be signed in to change notification settings - Fork 152
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
Upgrade node and dependencies? #992
Comments
Hi @schoettl 👋
I'm definitively in favor of upgrading node👍
Since organice is a SPA, hosting is not affected. As long as the regular dev, testing and build tools work. These tasks should run:
CI should run. We will have to update the Docker image which includes the node version. Lastly, a manual integration test should be done. As long as the sample and logins still work, I think we should be in the clear.
Sure, let's do it! I endeavoured into a first start: #993 |
Nice! I'll pick it up. |
On my system, the node version is 20.15.1 whereas organice uses 12.13.1.
There are many open dependabot PRs and
yarn audit
tells about 637 vulnerabilities.How about trying an upgrade @munen?
Apart from
yarn test
, CI and basic manual integration test – what do we need to safely upgrade? I've never done this before.How would staging or production cope with such changes? Should we give it a try, starting with node itself?
The text was updated successfully, but these errors were encountered: