Skip to content

chore(deps): update dependency @vercel/ncc to ^0.44.0#962

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vercel-ncc-0.x
Open

chore(deps): update dependency @vercel/ncc to ^0.44.0#962
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vercel-ncc-0.x

Conversation

@renovate

@renovate renovate Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@vercel/ncc ^0.38.4^0.44.0 age confidence

Release Notes

vercel/ncc (@​vercel/ncc)

v0.44.0

Compare Source

Features

v0.43.0

Compare Source

Changes

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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 94dc3b5ceb

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package-lock.json
"node": ">=18"
}
},
"node_modules/mongoose/node_modules/mongodb": {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore the nested gcp-metadata lock entry

Deleting the lock entry immediately before this package leaves package-lock.json out of sync with package.json: mongodb@7.2.0 still declares the optional peer gcp-metadata@^7.0.1, but the matching node_modules/mongoose/node_modules/gcp-metadata package is no longer in the lockfile. On this branch, npm ci --dry-run fails with Missing: gcp-metadata@ from lock file, so the npm ci steps in the test/check-dist workflows will block this dependency update until the lockfile is regenerated without dropping that entry.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants