Skip to content

[release-4.20] CONSOLE-5011: migrate to yarn berry#16070

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.20from
logonoff:CONSOLE-5011-4.20-core
Mar 9, 2026
Merged

[release-4.20] CONSOLE-5011: migrate to yarn berry#16070
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.20from
logonoff:CONSOLE-5011-4.20-core

Conversation

@logonoff
Copy link
Member

This is an automated cherry-pick of #16059

@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 26, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 26, 2026

@logonoff: This pull request references CONSOLE-5011 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target only the "4.20.z" version, but multiple target versions were set.

Details

In response to this:

This is an automated cherry-pick of #16059

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 26, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9acc79d8-2c0a-4791-b1cb-153b358493b6

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger 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.

@logonoff
Copy link
Member Author

Normally we wouldn't backport tech debt like this but it's unfortunately required this time

/label backport-risk-assessed

/assign @XiyunZhao @jhadvig

@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 26, 2026
@openshift-ci openshift-ci bot requested review from rawagner and rhamilto February 26, 2026 15:01
@openshift-ci openshift-ci bot added component/core Related to console core functionality component/dev-console Related to dev-console component/helm Related to helm-plugin component/knative Related to knative-plugin component/sdk Related to console-plugin-sdk component/topology Related to topology labels Feb 26, 2026
@logonoff logonoff force-pushed the CONSOLE-5011-4.20-core branch from 3806055 to c5b62fa Compare February 26, 2026 15:20
@logonoff logonoff force-pushed the CONSOLE-5011-4.20-core branch 3 times, most recently from 3fec77d to 6a04358 Compare February 27, 2026 17:09
@vojtechszocs
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2026
@logonoff logonoff force-pushed the CONSOLE-5011-4.20-core branch from 6a04358 to 8822830 Compare February 27, 2026 20:30
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2026
@jhadvig jhadvig added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 2, 2026
Copy link
Member

@jhadvig jhadvig 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 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. and removed lgtm Indicates that a PR is ready to be merged. labels Mar 2, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 7, 2026

New changes are detected. LGTM label has been removed.

@logonoff logonoff force-pushed the CONSOLE-5011-4.20-core branch from 6ec0e41 to abd35f7 Compare March 7, 2026 19:53
@openshift-ci openshift-ci bot added component/backend Related to backend component/gitops Related to gitops-plugin component/pipelines Related to pipelines-plugin labels Mar 7, 2026
@logonoff logonoff force-pushed the CONSOLE-5011-4.20-core branch 2 times, most recently from 857787b to 5dd9e79 Compare March 8, 2026 00:01
I get this problem in a sandbox cluster too (4.20.14):

Import is not possible.
Failed to parse devfile: mkdir docker: permission denied
@logonoff logonoff force-pushed the CONSOLE-5011-4.20-core branch from 5dd9e79 to 671dfbe Compare March 8, 2026 00:05
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 8, 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.

@XiyunZhao
Copy link
Contributor

XiyunZhao commented Mar 9, 2026

/verified by @XiyunZhao
No issues were found during local testing in the ./console and ./console/frontend directories. The following are part of the test steps

# 1. Verify environment
cd .console4.20/frontend
yarn --version                           # Should display 4.12.0
cat .yarnrc.yml | grep enableScripts     # Should be false

# 2. Check and Run core tests
cd ./consol4.20
./test-frontend.sh                       # Run all frontend tests
./build.sh                               # Perform the full build

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

@XiyunZhao: This PR has been marked as verified by @XiyunZhao.

Details

In response to this:

/verified by @XiyunZhao
No issues were found during local testing in the ./console and ./console/frontend directories. The following are part of the test steps

# 1. Verify environment
cd .console4.20/frontend
yarn --version                           # Should display 4.12.0
cat .yarnrc.yml | grep enableScripts     # Should be false

# 2. Check and Run core tests
cd /home/xiyuzhao/Zxy/Project/consol4.20
./test-frontend.sh                       # Run all frontend tests
./build.sh                               # Perform the full build

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.

@jhadvig
Copy link
Member

jhadvig commented Mar 9, 2026

/lgtm

@jhadvig jhadvig added the lgtm Indicates that a PR is ready to be merged. label Mar 9, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, logonoff, 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-merge-bot openshift-merge-bot bot merged commit 30da3fd into openshift:release-4.20 Mar 9, 2026
7 checks passed
@logonoff logonoff deleted the CONSOLE-5011-4.20-core branch March 9, 2026 14: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/backend Related to backend component/core Related to console core functionality component/dev-console Related to dev-console component/gitops Related to gitops-plugin component/helm Related to helm-plugin component/knative Related to knative-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.

8 participants