-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
update node to 18.17.1 #18525
update node to 18.17.1 #18525
Conversation
234847a
to
8d69efa
Compare
8d4b4b9
to
65d1945
Compare
65d1945
to
d95deaf
Compare
@jeanp413 it seems that checkboxes have stopped working 🤔 |
@filiptronicek fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested everything I reasonably could from starting workspaces (dashboard iframe and supervisor-frontend) to the user preferences and projects.
Looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a pass through on the dashboard and surprisingly it looks good despite how much changed. Left a couple comments but none are blocking. Going to hold off on approval on this as I know there was more testing and looking at this folks wanted to do.
@@ -4,6 +4,10 @@ | |||
* See License.AGPL.txt in the project root for license information. | |||
*/ | |||
|
|||
@tailwind base; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume we need to have this at the beginning of any css file where we're using a tailwind directive now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
supposedly it shouldn't be needed with the postcss-import
plugin in the postcss.config.js
but I spend a lot of time yesterday trying to make it work but couldn't 😞
because it was just three files for now I just copy the directive, but it would be good to fix it later
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested various SCM flows, workspace start, use of API related features, killing ws-manager, configured SSO (could not use ti because of mess with accounts). But everything seem to work, and don't see anything suspicious in logs.
/unhold |
Description
Summary generated by Copilot
🤖 Generated by Copilot at f2eb927
Updated the node version from 16.x to 18.17.1 in the Dockerfiles for several gitpod components and the dev image. Added an environment variable to enable the openssl-legacy-provider option for node 18 compatibility.
Related Issue(s)
Fixes #
How to test
Documentation
Preview status
Gitpod was successfully deployed to your preview environment.
Build Options
Build
Run the build with werft instead of GHA
Run Leeway with
--dont-test
Publish
Installer
Add desired feature flags to the end of the line above, space separated
Preview Environment / Integration Tests
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh
. If enabled,with-preview
andwith-large-vm
will be enabled./hold