chore(devdeps): update dependency verdaccio to v6.2.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
verdaccio (source)	6.2.1 → 6.2.4

---

Release Notes

verdaccio/verdaccio (verdaccio)

v6.2.4

Compare Source

What's Changed

• fix: allow docker listen address to be configured (6.x) by @​markormesher in #​5503

VERDACCIO_ADDRESS Environment Variable for Docker

You can now set the VERDACCIO_ADDRESS environment variable to control Verdaccio’s network bind address.

• Choose IPv4 (0.0.0.0), IPv6 ([::]), or a specific interface.
• Improves compatibility for dual-stack and custom environments.

Example:

docker run -e VERDACCIO_ADDRESS=0.0.0.0 ...
docker run -e VERDACCIO_ADDRESS='[::]' ...

More info at : https://verdaccio.org/docs/env/

Full Changelog: verdaccio/verdaccio@v6.2.3...v6.2.4

v6.2.3

Compare Source

What's Changed

• fix(deps): update core verdaccio dependencies (6.x) by @​renovate[bot] in #​5497
  • fix(middleware): dist-tags with scoped packages #​5495 https://redirect.github.com/orgs/verdaccio/discussions/5483 @​mbtools and @​stgbmpi
• fix: Docker image not listening on IPv6 (6.x) by @​A1bi in #​5499 (🐛 regression) will be fixed at v6.2.4

Full Changelog: verdaccio/verdaccio@v6.2.2...v6.2.3

v6.2.2

Compare Source

What's Changed

• fix(deps): update core verdaccio dependencies (6.x) by @​renovate[bot] in #​5477
  • fix: running without auth plugin (#​5466) @​mbtools
• fix(deps): update core verdaccio dependencies (6.x) by @​renovate[bot] in #​5488
  • fix: notification packages bug #​5439 @​juanpicado
  • chore: replace mime package with constants (#​5471) @​mbtools
  • fix(proxy): proxy protocol check (#​5474) @​mbtools
• fix(deps): update dependency semver to v7.7.3 (6.x) by @​renovate[bot] in #​5489
• chore(deps): update node.js to v22.21.1 (6.x) by @​renovate[bot] in #​5491
• chore(deps): update babel monorepo to v7.28.5 (6.x) by @​renovate[bot] in #​5490
• fix(deps): update core verdaccio dependencies (6.x) by @​renovate[bot] in #​5493

Full Changelog: verdaccio/verdaccio@v6.2.1...v6.2.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: aa71129

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

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

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

[nx-cloud]

View your CI Pipeline Execution ↗ for commit aa71129

Command	Status	Duration	Result
nx affected -t build lint test e2e-ci	❌ Failed	2m 24s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-01-14 17:33:35 UTC

[nx-cloud]

Nx Cloud has identified a possible root cause for your failed CI:

Our analysis indicates this webServer timeout is likely an environment issue rather than a code regression. The PR only updates verdaccio (running on port 4873), while the failing component is the Vite dev server on port 8443 with no configuration changes. This appears to be a resource contention or infrastructure timing issue during test execution.

No code changes were suggested for this issue.

If the issue was transient, you can trigger a rerun:

View detailed reasoning on Nx Cloud ↗

_{🎓 Learn more about Self-Healing CI on nx.dev}