Skip to content

[release-4.18] NO-JIRA: Bump builder image to v29#15995

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.18from
logonoff:4.18-fixes
Feb 6, 2026
Merged

[release-4.18] NO-JIRA: Bump builder image to v29#15995
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.18from
logonoff:4.18-fixes

Conversation

@logonoff
Copy link
Member

@logonoff logonoff commented Feb 4, 2026

See https://issues.redhat.com/browse/CONSOLE-5071

This PR (and its "backports" all the way to 4.12) aim to add compatibility with node.js 22/24 when building console.

This is because yarn berry requires at least node 18, and we will probably want to consistently use our tectonic-console-builder:v29 image across these versions.

For 4.19+, we are already using webpack 5 due to #14378, so there is already node.js 18+ support. The package.json script changes can instead be merged later when we update yarn to v4.

Changes:

Note: the list of changes are descriptive for all backport PRs. Some of these changes may not apply to every backport.

4.18 to 4.12

  • Format the dependencies field of applicable package.json files to align with yarn berry's auto formatting
  • Remove the for loop in yarn compile in the dynamic plugin sdk. This syntax no longer works in yarn berry, and having separate scripts is also more readable
  • Bump image build root to tectonic-console-builder:v29 to get node 22 (which is needed for yarn v4)
  • Bump webpack and terser-webpack-plugin to get their md4 polyfill, which is used just for file names. This is required for node 18+ support

4.16 to 4.12

  • Removed reviewer responsibility from people who have left the project (by request of former dev-console team members)

4.14 to 4.12

  • Install Chrome for Testing to get Protractor working. tectonic-console-builder:v29 does not include the required Chrome v114 required to run the tests

4.13 to 4.12

Backports:

@openshift-ci-robot
Copy link
Contributor

@logonoff: This pull request explicitly references no jira issue.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 4, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 4, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot added component/core Related to console core functionality component/dev-console Related to dev-console approved Indicates a PR has been approved by an approver from all required OWNERS files. component/sdk Related to console-plugin-sdk component/topology Related to topology labels Feb 4, 2026
@vojtechszocs
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@logonoff
Copy link
Member Author

logonoff commented Feb 4, 2026

these are dev dependency changes that do not affect the build
/verified by CI

@logonoff
Copy link
Member Author

logonoff commented Feb 4, 2026

/label backport-risk-assessed

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 4, 2026
@openshift-ci-robot
Copy link
Contributor

@logonoff: This PR has been marked as verified by CI.

Details

In response to this:

these are dev dependency changes that do not affect the build
/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 4, 2026
@openshift-ci-robot
Copy link
Contributor

@logonoff: This pull request explicitly references no jira issue.

Details

In response to this:

This PR (and its "backports" all the way to 4.12) aim to add compatibility with node.js 22 when building console.

This is because yarn berry requires at least node 18, and we will probably want to consistently use our tectonic-console-builder:v29 image across these versions.

For 4.19+, we are already using webpack 5 due to #14378, so there is already node.js 18+ support. The package.json script changes can instead be merged later when we update yarn to v4.

Changes:

  • Where applicable, removed reviewer responsibility from people who have left the project
  • Bump webpack and terser-webpack-plugin to get their md4 polyfill, which is used just for file names. This is required for node 18+ support
  • Bump ts-json-schema-generator to at least 0.93.0 (and typescript to 4.47.0), which removes usage of deprecated node utils, which is removed in node 23
  • In the doc parser script, backport getCommentText
  • Rename yarn eslint script to lint-files because yarn berry no longer supports shadowing of this kind
  • Format the dependencies field of applicable package.json files to align with yarn berry's auto formatting
  • Remove the for loop in yarn compile in the dynamic plugin sdk. This syntax no longer works in yarn berry, and having separate scripts is also more readable

Backports:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Feb 4, 2026
@openshift-ci openshift-ci bot removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 4, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

@logonoff: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@logonoff
Copy link
Member Author

logonoff commented Feb 6, 2026

/retitle [release-4.18] NO-JIRA: Bump builder image to v29

@openshift-ci openshift-ci bot changed the title [release-4.18] NO-JIRA: Build compatibility with node 22 [release-4.18] NO-JIRA: Bump builder image to v29 Feb 6, 2026
@logonoff
Copy link
Member Author

logonoff commented Feb 6, 2026

changes only affect devdependencies and node version

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 6, 2026
@openshift-ci-robot
Copy link
Contributor

@logonoff: This PR has been marked as verified by CI.

Details

In response to this:

changes only affect devdependencies and node version

/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Contributor

@logonoff: This pull request explicitly references no jira issue.

Details

In response to this:

See https://issues.redhat.com/browse/CONSOLE-5071

This PR (and its "backports" all the way to 4.12) aim to add compatibility with node.js 22/24 when building console.

This is because yarn berry requires at least node 18, and we will probably want to consistently use our tectonic-console-builder:v29 image across these versions.

For 4.19+, we are already using webpack 5 due to #14378, so there is already node.js 18+ support. The package.json script changes can instead be merged later when we update yarn to v4.

Changes:

  • Where applicable, removed reviewer responsibility from people who have left the project
  • Bump webpack and terser-webpack-plugin to get their md4 polyfill, which is used just for file names. This is required for node 18+ support
  • Bump ts-json-schema-generator to at least 0.93.0 (and typescript to 4.47.0), which removes usage of deprecated node utils, which is removed in node 23
  • In the doc parser script, backport changes to getCommentText that made the function work in TypeScript 4.47.0
  • Format the dependencies field of applicable package.json files to align with yarn berry's auto formatting
  • Remove the for loop in yarn compile in the dynamic plugin sdk. This syntax no longer works in yarn berry, and having separate scripts is also more readable
  • Bump image build root to tectonic-console-builder:v29 for node 22
  • Where applicable, install Chrome for Testing to get Protractor working. tectonic-console-builder:v29 does not include the required Chrome v114 required to run the tests

Backports:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Member

@TheRealJon TheRealJon left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, TheRealJon, vojtechszocs

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2026
@jhadvig jhadvig added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 6, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit ea9fa22 into openshift:release-4.18 Feb 6, 2026
8 checks passed
@logonoff logonoff deleted the 4.18-fixes branch February 6, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. component/core Related to console core functionality component/dev-console Related to dev-console component/sdk Related to console-plugin-sdk component/topology Related to topology jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants