Skip to content

fix(deps): update dependency next to v16.3.5 - #520

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nextjs-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nextjs-monorepo

Conversation

@renovate

@renovate renovate Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
next (source) 16.3.316.3.5 age confidence

Release Notes

vercel/next.js (next)

v16.3.5

Compare Source

v16.3.4

Compare Source


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 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 renovate Bot added the dependencies Pull requests that update a dependency file label Sep 14, 2026
@renovate

renovate Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: pnpm-lock.yaml
Error: ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION

  × installing dependencies
  ╰─▶ 11 lockfile entries failed verification:
        lefthook-darwin-arm64@2.1.14 was published at 2026-09-
      14T10:25:59.000Z, within the minimumReleaseAge cutoff (2026-09-
      13T13:17:44.661Z)
        lefthook-darwin-x64@2.1.14 was published at 2026-09-14T10:26:06.000Z,
      within the minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
        lefthook-freebsd-arm64@2.1.14 was published at 2026-09-
      14T10:26:39.000Z, within the minimumReleaseAge cutoff (2026-09-
      13T13:17:44.661Z)
        lefthook-freebsd-x64@2.1.14 was published at 2026-09-14T10:26:46.000Z,
      within the minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
        lefthook-linux-arm64@2.1.14 was published at 2026-09-14T10:26:13.000Z,
      within the minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
        lefthook-linux-x64@2.1.14 was published at 2026-09-14T10:26:19.000Z,
      within the minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
        lefthook-openbsd-arm64@2.1.14 was published at 2026-09-
      14T10:26:52.000Z, within the minimumReleaseAge cutoff (2026-09-
      13T13:17:44.661Z)
        lefthook-openbsd-x64@2.1.14 was published at 2026-09-14T10:26:59.000Z,
      within the minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
        lefthook-windows-arm64@2.1.14 was published at 2026-09-
      14T10:26:26.000Z, within the minimumReleaseAge cutoff (2026-09-
      13T13:17:44.661Z)
        lefthook-windows-x64@2.1.14 was published at 2026-09-14T10:26:32.000Z,
      within the minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
        lefthook@2.1.14 was published at 2026-09-14T10:27:04.000Z, within the
      minimumReleaseAge cutoff (2026-09-13T13:17:44.661Z)
  help: The lockfile contains entries that the active policies reject. This
        can mean the lockfile is stale, or that someone committed a lockfile
        that bypassed the policy locally — inspect recent changes to pnpm-
        lock.yaml before trusting it. If the changes look expected, run "pnpm
        clean --lockfile" and then "pnpm install" to rebuild from a fresh
        resolution. Alternatively, relax the policy that flagged them.


@coderabbitai

coderabbitai Bot commented Sep 14, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 58e3ec95-4f3d-4974-9968-9bb3e27d8ec4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key: "path_filters"
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants