Update dependency upgrades - non-major

renovate[bot] commented 4 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@next/eslint-plugin-next (source)	`14.2.3` -> `14.2.4`
@typescript-eslint/utils (source)	`7.12.0` -> `7.13.0`
@vitejs/plugin-react (source)	`4.3.0` -> `4.3.1`
pnpm (source)	`9.2.0` -> `9.3.0`
prettier (source)	`3.3.1` -> `3.3.2`
vite (source)	`5.2.12` -> `5.3.0`

Release Notes

vercel/next.js (@next/eslint-plugin-next)

### [`v14.2.4`](https://togithub.com/vercel/next.js/releases/tag/v14.2.4) [Compare Source](https://togithub.com/vercel/next.js/compare/v14.2.3...v14.2.4) > \[!NOTE]\ > This release is backporting bug fixes. It does **not** include all pending features/changes on canary. ##### Core Changes - fix: ensure route handlers properly track dynamic access ([#66446](https://togithub.com/vercel/next.js/issues/66446)) - fix NextRequest proxy in edge runtime ([#66551](https://togithub.com/vercel/next.js/issues/66551)) - Fix next/dynamic with babel and src dir ([#65177](https://togithub.com/vercel/next.js/issues/65177)) - Use vercel deployment url for metadataBase fallbacks ([#65089](https://togithub.com/vercel/next.js/issues/65089)) - fix(next/image): detect react@19 for fetchPriority prop ([#65235](https://togithub.com/vercel/next.js/issues/65235)) - Fix loading navigation with metadata and prefetch ([#66447](https://togithub.com/vercel/next.js/issues/66447)) - prevent duplicate RSC fetch when action redirects ([#66620](https://togithub.com/vercel/next.js/issues/66620)) - ensure router cache updates reference the latest cache values ([#66681](https://togithub.com/vercel/next.js/issues/66681)) - Prevent append of trailing slash in cases where path ends with a file extension ([#66636](https://togithub.com/vercel/next.js/issues/66636)) - Fix inconsistency with 404 getStaticProps cache-control ([#66674](https://togithub.com/vercel/next.js/issues/66674)) - Use addDependency to track metadata route file changes ([#66714](https://togithub.com/vercel/next.js/issues/66714)) - Add timeout/retry handling for fetch cache ([#66652](https://togithub.com/vercel/next.js/issues/66652)) - fix: app-router prefetch crash when an invalid URL is passed to Link ([#66755](https://togithub.com/vercel/next.js/issues/66755)) ##### Credits Huge thanks to [@ztanner](https://togithub.com/ztanner), [@ijjk](https://togithub.com/ijjk), [@wbinnssmith](https://togithub.com/wbinnssmith), [@huozhi](https://togithub.com/huozhi), and [@lubieowoce](https://togithub.com/lubieowoce) for helping!

typescript-eslint/typescript-eslint (@typescript-eslint/utils)

### [`v7.13.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/utils/CHANGELOG.md#7130-2024-06-10) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v7.12.0...v7.13.0) This was a version bump only for utils to align it with other projects, there were no code changes. You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

vitejs/vite-plugin-react (@vitejs/plugin-react)

### [`v4.3.1`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#431-2024-06-10) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.3.0...v4.3.1) ##### Fix support for React Compiler with React 18 The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom `runtimeModule`: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43 When using a custom `runtimeModule`, the plugin will not try to pre-optimize `react/compiler-runtime` dependency. Reminder: Vite expect code outside of `node_modules` to be ESM, so you will need to update the gist with `import React from 'react'`.

pnpm/pnpm (pnpm)

### [`v9.3.0`](https://togithub.com/pnpm/pnpm/releases/tag/v9.3.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v9.2.0...v9.3.0) #### Minor Changes - **Semi-breaking.** Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the `peers-suffix-max-length` setting [#8177](https://togithub.com/pnpm/pnpm/pull/8177). #### Patch Changes - Set `reporter-hide-prefix` to `true` by default for `pnpm exec`. In order to show prefix, the user now has to explicitly set `reporter-hide-prefix=false` [#8174](https://togithub.com/pnpm/pnpm/issues/8174). #### Platinum Sponsors

#### Gold Sponsors

#### Our Silver Sponsors

prettier/prettier (prettier)

### [`v3.3.2`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#332) [Compare Source](https://togithub.com/prettier/prettier/compare/3.3.1...3.3.2) [diff](https://togithub.com/prettier/prettier/compare/3.3.1...3.3.2) ##### Fix handlebars path expressions starts with `@` ([#16358](https://togithub.com/prettier/prettier/pull/16358) by [@Princeyadav05](https://togithub.com/Princeyadav05)) ```hbs {{! Input }}

```

vitejs/vite (vite)

### [`v5.3.0`](https://togithub.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#530-2024-06-13) [Compare Source](https://togithub.com/vitejs/vite/compare/v5.2.13...v5.3.0) - fix: typo in client log ([#17363](https://togithub.com/vitejs/vite/issues/17363)) ([68aa9f8](https://togithub.com/vitejs/vite/commit/68aa9f8)), closes [#17363](https://togithub.com/vitejs/vite/issues/17363) - fix(ssrTransform): handle arbitrary module namespace identifiers ([#17446](https://togithub.com/vitejs/vite/issues/17446)) ([0a76652](https://togithub.com/vitejs/vite/commit/0a76652)), closes [#17446](https://togithub.com/vitejs/vite/issues/17446) - test: disable isolate for unit test ([#17448](https://togithub.com/vitejs/vite/issues/17448)) ([f16fae5](https://togithub.com/vitejs/vite/commit/f16fae5)), closes [#17448](https://togithub.com/vitejs/vite/issues/17448) - feat: asset type add bmp ([#17439](https://togithub.com/vitejs/vite/issues/17439)) ([ec287f8](https://togithub.com/vitejs/vite/commit/ec287f8)), closes [#17439](https://togithub.com/vitejs/vite/issues/17439) ### [`v5.2.13`](https://togithub.com/vitejs/vite/releases/tag/v5.2.13) [Compare Source](https://togithub.com/vitejs/vite/compare/v5.2.12...v5.2.13) Please refer to [CHANGELOG.md](https://togithub.com/vitejs/vite/blob/v5.2.13/packages/vite/CHANGELOG.md) for details.

Configuration

📅 Schedule: Branch creation - "after 4pm on thursday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 4 months ago

⚠️ 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

Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 104, reused 0, downloaded 0, added 0
Progress: resolved 197, reused 0, downloaded 0, added 0
Progress: resolved 397, reused 0, downloaded 0, added 0
Progress: resolved 506, reused 0, downloaded 0, added 0
undefined
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: @vitejs/plugin-react@4.3.0

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

renovate[bot] commented 4 months ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

karlhorky / archive-webpage-browser-extension