ART-18353: switch networking-console-plugin pkg_managers from yarn to npm (4.19)

[joepvd]

Summary

Switch pkg_managers from yarn to npm for networking-console-plugin on openshift-4.19.

Same fix as PR for ART-18521 (openshift-4.18). The upstream source uses package-lock.json
(npm), not yarn.lock. The hermeto/yarn prefetch handler fails because it cannot determine
the yarn version. This aligns with openshift-4.20 which already uses pkg_managers: [npm].

Failing build: https://art-build-history-art-build-history.apps.artc2023.pc3z.p1.openshiftapps.com/?name=^networking-console-plugin$&group=openshift-4.19&assembly=stream&engine=konflux&outcome=failure

Analysis

The hermeto prefetch step fails with:

ERROR PackageRejected: Unable to determine the yarn version to use to process the request

The upstream repo has package-lock.json (npm) across all branches. The 4.20 config
already uses pkg_managers: [npm] and builds fine.

Changes

• Changed content.source.pkg_managers from [yarn] to [npm]

Generated with Claude Code

[openshift-ci-robot]

@joepvd: This pull request references ART-18353 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 task to target the "4.19.z" version, but no target version was set.

Details

In response to this:

Summary

Switch pkg_managers from yarn to npm for networking-console-plugin on openshift-4.19.

Same fix as PR for ART-18521 (openshift-4.18). The upstream source uses package-lock.json
(npm), not yarn.lock. The hermeto/yarn prefetch handler fails because it cannot determine
the yarn version. This aligns with openshift-4.20 which already uses pkg_managers: [npm].

Failing build: https://art-build-history-art-build-history.apps.artc2023.pc3z.p1.openshiftapps.com/?name=^networking-console-plugin$&group=openshift-4.19&assembly=stream&engine=konflux&outcome=failure

Analysis

The hermeto prefetch step fails with:

ERROR PackageRejected: Unable to determine the yarn version to use to process the request

The upstream repo has package-lock.json (npm) across all branches. The 4.20 config
already uses pkg_managers: [npm] and builds fine.

Changes

• Changed content.source.pkg_managers from [yarn] to [npm]

Generated with Claude Code

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign germanparente for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[joepvd]

Triggered seed-lockfile test build #394 to verify (ASSEMBLY=test, data from this PR branch).

[openshift-ci]

@joepvd: 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/art-pre-commit-check	d2a6d72	link	false	/test art-pre-commit-check

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.