Update dependency @vercel/ncc to v0.44.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vercel/ncc	0.44.0 → 0.44.1
@vercel/ncc	0.44.0 → 0.44.1

---

Release Notes

vercel/ncc (@​vercel/ncc)

v0.44.1

Compare Source

v0.44.0

Compare Source

Features

• read permissions pr.yml (#​1323) (5ea625e)

v0.43.0

Compare Source

Changes

• BREAKING CHANGE: add Node 24 and 26 support, remove 20 (#​1318) (#​1305)
• switch npm releases to trusted publishing (OIDC) (#​1325) (#​1327) (#​1328) (#​1329) (#​1330) (#​1331) (#​1332)
• switch package management to pnpm (#​1321)
• fix predictable global cache directory in /tmp enables symlink/hijack risks (#​1314)
• reorder extension resolution to prioritise TypeScript over JSON (#​1315)
• support TypeScript 6 transpile builds (#​1316)

v0.38.4

Compare Source

Bug Fixes

• cjs-build: enable evaluating import.meta in cjs build (#​1236) (e72d34d), closes /github.com/vercel/ncc/pull/897#discussion_r836916315 #​1019

v0.38.3

Compare Source

Bug Fixes

• add missing --asset-builds to cli help message (#​1228) (84f8c52)

v0.38.2

Compare Source

Bug Fixes

• deps: update webpack to v5.94.0, terser to v5.33.0 (#​1213) (158a1fd), closes #​1193 #​1194 #​1177 #​1204 #​1195

Huge thanks to @​theoludwig 🎉

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 artifacts 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: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
bench/vercel                             |  WARN  deprecated term-size@4.0.0
packages/create-next-app                 |  WARN  deprecated @types/ci-info@3.1.4
packages/eslint-plugin-next              |  WARN  deprecated @types/glob@9.0.0
packages/eslint-plugin-next              |  WARN  deprecated glob@10.5.0
packages/eslint-plugin-next              |  WARN  deprecated eslint@8.57.1
packages/next                            |  WARN  deprecated @babel/plugin-proposal-class-properties@7.18.6
packages/next                            |  WARN  deprecated @babel/plugin-proposal-export-namespace-from@7.18.9
packages/next                            |  WARN  deprecated @babel/plugin-proposal-numeric-separator@7.18.6
packages/next                            |  WARN  deprecated @babel/plugin-proposal-object-rest-spread@7.20.7
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@next%2Fswc: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next

@next/swc is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

File name: .github/pnpm-lock.yaml

[ERR_PNPM_UNSUPPORTED_ENGINE] Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/tmp/renovate/repos/github/X-oss-byte/Nextjs/.github/actions/next-stats-action".

Expected version: 9.15.9
Got: 11.9.0

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: cf7eb15

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.

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