chore(deps): update dependency np to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
np	^10.0.0 → ^11.0.0

---

Release Notes

sindresorhus/np (np)

v11.2.1

Compare Source

• Skip Node.js engine check for prerelease-to-prerelease bumps abfe30b

---

v11.2.0

Compare Source

• Add devEngines.packageManager support (#​789) 03d4787

---

v11.1.0

Compare Source

• Run Git preflight before prompting (#​788) 8658708
• Add --dry-run as an alias of --preview d24cb95
• Run install even with --no-cleanup 2677fcc
• Fix: Use empty prerelease default for pre-major bump 86a7f26

---

v11.0.3

Compare Source

• Fix --release-draft-only failing with version check error 06a142c
• Fix: Skip missing entry points for lifecycle-built packages (#​782) 6d4b88e

---

v11.0.2

Compare Source

• Fix: Allow raising Node.js engine requirement in pre-1.0.0 packages f0859d9

---

v11.0.1

Compare Source

• Fix Trusted Publishing via OIDC (#​777) e6a8daf

---

v11.0.0

Compare Source

Breaking

• Require Node.js 20 307ebec

Improvements

• Support passkey authentication via automatic browser opening 1ef9af7
• Support publishing via OIDC authentication (#​772) 3ded31e
• Add --no-release-notes flag 4f910a2
• Add --remote flag to specify Git remote 4d5fb6a
• Add prerequisite check for package entry points 7dcd833
• Require major version bump when dropping Node.js support 3ed286a
• Add interactive prerelease identifier selection 6b51dda
• Support GPG password prompts during version bumping 5a96f80
• Show unpublished files as warning instead of blocking prompt efcc05e
• Add npm provenance support d8f3322
• Add git user configuration check to prevent npm version failures ebb9acf

Fixes

• Fix --contents flag not being respected when publishing 53904d0
• Fix compatibility with some external registries c6ef15d
• Fix repository URL parsing for shorthand and GitHub Enterprise URLs 02b4ed9
• Fix Yarn Berry detection when packageManager field is missing 7009b77
• Fix ENOWORKSPACES error when publishing from monorepo workspace 0a8af7b
• Fix rejection of explicit version numbers ebdcbaa
• Fix publish hanging indefinitely a651fc4
• Fix first publish failure for prerelease versions with npm 10+ 3811182
• Fix subfolder publishing broken since npm 8.5 e996c6f
• Fix CLI default flags overriding local config values 3804d0b
• Fix publishConfig handling for access and registry fields 753abb4
• Fix npm pack JSON parsing when lifecycle scripts output to stdout a13bba2
• Fix git commands failing with password-protected SSH keys 67b6aff
• Fix failure with repositories that have multiple initial commits 869f80b
• Fix package.json config being ignored with global installation 08a3f64
• Fix long release notes exceeding GitHub URL limit a160aff
• Fix some network calls never timing out 6a11153
• Fix contents config option being ignored 88226d7
• Fix contents option being interpreted as package name 521ecfc
• Fix incorrect commit range when tags are created out of order fea3eb7
• Fix getNpmPackageAccess to respect publishConfig.registry 15040c8
• Fix authentication when publishConfig.registry is official npm registry 380fd24

---

v10.3.0

Compare Source

• Auto-run npm login on authentication failure 38abeee
• Include stderr in error message for failed commands 0ad9a8c
• Fix rollback not executing when publish fails 005ebdb

---

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: np@11.2.1
npm ERR! notsup Not compatible with your version of node/npm: np@11.2.1
npm ERR! notsup Required: {"node":">=20","npm":">=9","git":">=2.11.0","yarn":">=1.7.0","pnpm":">=8","bun":">=1"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v22.22.3"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-06-01T18_47_06_062Z-debug-0.log