Fix/rocket/ep 9545 try fixing lerna publish

[Michael Ignoto (Ignotos)]

Jira issue link: EP-9545

The lerna publish is failing with a classically cryptic 404 error that tells us nothing 😔 https://github.com/workleap/ov-igloo-ui/actions/runs/22917927750/job/66512006908

The logs before it fails seems to hint that we are trying to publish to a registry that is not the default npm one, but we want to publish them there

lerna info auto-confirmed lerna info publish Publishing packages to npm... lerna notice Skipping all user and access validation due to third-party registry lerna notice Make sure you're authenticated properly ¯\_(ツ)_/¯ lerna ERR! E404 Not found error Command failed with exit code 1.

Trying to see if setting the registry explicitly for the publish command fixes it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: cfbfab6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull request overview

This PR attempts to resolve the lerna publish CI failure (cryptic 404) by explicitly configuring Lerna’s publish command to use the public npm registry (https://registry.npmjs.org) instead of an unintended registry.

Changes:

• Moves the registry setting out of command.version and into command.publish.
• Keeps command.version configuration (release commit message + allowed branches) unchanged in behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.