Skip to content
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

use latest node 18.18.0 in workflows #2783

Merged
merged 1 commit into from
Oct 11, 2023
Merged

use latest node 18.18.0 in workflows #2783

merged 1 commit into from
Oct 11, 2023

Conversation

nickboldt
Copy link
Collaborator

@nickboldt nickboldt commented Oct 10, 2023

What does this PR do?

use latest node 18.18.0 in workflows

Change-Id: Id9133f0e7f6bb738f8625fd3bdc79730df6a004e
Signed-off-by: Nick Boldt [email protected]

bump copyrights

Change-Id: I3bc89c21ae5b5255559684ff9682564aa7729bcf
Signed-off-by: Nick Boldt [email protected]

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

none; this might also be unsafe due to microsoft/vscode#194665

How to test this PR?

N/A

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Change-Id: Id9133f0e7f6bb738f8625fd3bdc79730df6a004e
Signed-off-by: Nick Boldt <[email protected]>

bump copyrights

Change-Id: I3bc89c21ae5b5255559684ff9682564aa7729bcf
Signed-off-by: Nick Boldt <[email protected]>
@openshift-ci
Copy link

openshift-ci bot commented Oct 10, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nickboldt

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nickboldt nickboldt changed the title use latest node 18.18.0 in... use latest node 18.18.0 in workflows Oct 10, 2023
@@ -23,7 +23,7 @@ jobs:
persist-credentials: false
- uses: actions/setup-node@v3
with:
node-version: 18.16.1
node-version: 18.18.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe it makes sense to try 18.15 version if the bug is still not fixed in the che-code?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nickboldt nickboldt marked this pull request as draft October 10, 2023 19:50
@tolusha tolusha marked this pull request as ready for review October 11, 2023 06:38
@tolusha tolusha merged commit 1ccd67b into main Oct 11, 2023
10 checks passed
@tolusha tolusha deleted the bump-to-node-18.18 branch October 11, 2023 09:31
@devstudio-release
Copy link

Build 3.10 :: dsc_3.x/1466: Console, Changes, Git Data

@devstudio-release
Copy link

Build 3.10 :: dsc_3.x/1466: SUCCESS

3.10.0-CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants