Skip to content

OCPBUGS-74424: migrate yarn 1 to npm (backport to release-4.21)#170

Open
upalatucci wants to merge 6 commits intoopenshift:release-4.21from
upalatucci:port-to-npm-4.21
Open

OCPBUGS-74424: migrate yarn 1 to npm (backport to release-4.21)#170
upalatucci wants to merge 6 commits intoopenshift:release-4.21from
upalatucci:port-to-npm-4.21

Conversation

@upalatucci
Copy link

Summary

  • Backport of the yarn-to-npm migration from main (PR OCPBUGS-74424: migrate yarn 1 to npm #161) to release-4.21
  • Replaces yarn.lock with package-lock.json and updates all scripts, Dockerfiles, and webpack config to use npm instead of yarn
  • Switches from ts-loader to esbuild-loader for faster builds

Changes

  • package.json: scripts migrated from yarn to npm, added esbuild-loader dependency, added @parcel/watcher override
  • Dockerfile / Dockerfile.art: switched from yarn to npm ci --ignore-scripts
  • webpack.config.ts: replaced ts-loader with esbuild-loader
  • start-console.sh / test-prow-e2e.sh: updated commands from yarn to npm
  • yarn.lock removed, package-lock.json added

Made with Cursor

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 26, 2026
@openshift-ci-robot
Copy link

@upalatucci: This pull request references Jira Issue OCPBUGS-74424, which is invalid:

  • expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.22.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-74424 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Backport of the yarn-to-npm migration from main (PR OCPBUGS-74424: migrate yarn 1 to npm #161) to release-4.21
  • Replaces yarn.lock with package-lock.json and updates all scripts, Dockerfiles, and webpack config to use npm instead of yarn
  • Switches from ts-loader to esbuild-loader for faster builds

Changes

  • package.json: scripts migrated from yarn to npm, added esbuild-loader dependency, added @parcel/watcher override
  • Dockerfile / Dockerfile.art: switched from yarn to npm ci --ignore-scripts
  • webpack.config.ts: replaced ts-loader with esbuild-loader
  • start-console.sh / test-prow-e2e.sh: updated commands from yarn to npm
  • yarn.lock removed, package-lock.json added

Made with Cursor

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

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.

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci bot requested review from avivtur and metalice February 26, 2026 16:51
@openshift-ci
Copy link

openshift-ci bot commented Feb 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: upalatucci

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

openshift-ci bot commented Feb 26, 2026

@upalatucci: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-tests 37c3abe link true /test e2e-tests

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.

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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants