Skip to content

Update dependency @vercel/nft to v0.27.6#3030

Merged
kodiakhq[bot] merged 1 commit intocanaryfrom
renovate/vercel-nft-0.x
Nov 6, 2024
Merged

Update dependency @vercel/nft to v0.27.6#3030
kodiakhq[bot] merged 1 commit intocanaryfrom
renovate/vercel-nft-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 6, 2024 •
edited by sourcery-ai bot
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vercel/nft 0.27.5 -> 0.27.6 age adoption passing confidence

Release Notes

vercel/nft (@​vercel/nft)

v0.27.6

Compare Source

Bug Fixes

v0.27.5

Compare Source

Bug Fixes

v0.27.4

Compare Source

Bug Fixes

v0.27.3

Compare Source

Bug Fixes

v0.27.2

Compare Source

Bug Fixes

v0.27.1

Compare Source

Bug Fixes

v0.27.0

Compare Source

Features

v0.26.5

Compare Source

Bug Fixes
  • Add special case for Serial Port binary (.node) modules (#​415) (e001d05)

Configuration

📅 Schedule: 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.

Summary by Sourcery

Build:

  • Update @vercel/nft dependency from version 0.27.5 to 0.27.6.

@renovate
Copy link
Contributor Author

renovate bot commented Nov 6, 2024

⚠️ 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
Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
bench/vercel                             |  WARN  deprecated term-size@4.0.0
.                                        |  WARN  deprecated @babel/plugin-proposal-object-rest-spread@7.20.7
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@turbo%2Fpack-test-harness: Not Found - 404

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

@turbo/pack-test-harness is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

@bolt-new-by-stackblitz
Copy link

bolt-new-by-stackblitz bot commented Nov 6, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@sourcery-ai
Copy link

sourcery-ai bot commented Nov 6, 2024 •
edited
Loading

Reviewer's Guide by Sourcery

This PR updates the @vercel/nft dependency from version 0.27.5 to 0.27.6 in the Next.js package. The update includes a bug fix related to the @mapbox/node-pre-gyp dependency.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Dependency version update in package.json
  • Updated @vercel/nft from 0.27.5 to 0.27.6
  • Includes bug fix for @mapbox/node-pre-gyp dependency update to version 1.0.11
 packages/next/package.json
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@kodiakhq kodiakhq bot merged commit 1bd8301 into canary Nov 6, 2024
@changeset-bot
Copy link

changeset-bot bot commented Nov 6, 2024

⚠️ No Changeset found

Latest commit: 423f3e5

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

@kodiakhq kodiakhq bot deleted the renovate/vercel-nft-0.x branch November 6, 2024 23:43
sourcery-ai[bot]
sourcery-ai bot reviewed Nov 6, 2024
View reviewed changes
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

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

Reviewers

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants