Skip to content

[release-4.12] NO-JIRA: Bump builder image to v29#15988

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

[release-4.12] NO-JIRA: Bump builder image to v29#15988
openshift-merge-bot[bot] merged 4 commits intoopenshift:release-4.12from
logonoff:4.12-fixes

Conversation

@logonoff
Copy link
Member

@logonoff logonoff commented Feb 4, 2026

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

This is an automated cherry-pick of #15989

@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
@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.

@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 component/sdk Related to console-plugin-sdk component/topology Related to topology labels Feb 4, 2026
@TheRealJon
Copy link
Member

TheRealJon commented Feb 4, 2026

Looks like there's an issue with the --openssl-legacy-provider flag, seeing errors in CI:

/usr/local/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS

@logonoff logonoff force-pushed the 4.12-fixes branch 3 times, most recently from 659a65a to e2e0d70 Compare February 4, 2026 17:46
@openshift-ci openshift-ci bot added component/ceph Related to ceph-storage-plugin component/git-service Related to git-service component/gitops Related to gitops-plugin component/helm Related to helm-plugin component/insights Related to insights plugin component/knative Related to knative-plugin component/metal3 Related to metal3-plugin component/pipelines Related to pipelines-plugin labels 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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@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-5011

This is an automated cherry-pick of #15989

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
@logonoff
Copy link
Member Author

logonoff commented Feb 6, 2026

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

@openshift-ci openshift-ci bot changed the title [release-4.12] NO-JIRA: Build compatibility with node 22 [release-4.12] NO-JIRA: Bump builder image to v29 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
@logonoff
Copy link
Member Author

logonoff commented Feb 6, 2026

/retest

@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.

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
@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.

@openshift-merge-bot openshift-merge-bot bot merged commit 744e003 into openshift:release-4.12 Feb 6, 2026
8 checks passed
@logonoff logonoff deleted the 4.12-fixes branch February 6, 2026 17:42
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/ceph Related to ceph-storage-plugin component/core Related to console core functionality component/dev-console Related to dev-console component/git-service Related to git-service component/gitops Related to gitops-plugin component/helm Related to helm-plugin component/insights Related to insights plugin component/knative Related to knative-plugin component/metal3 Related to metal3-plugin component/pipelines Related to pipelines-plugin 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