Repository navigation
Bump nuxt from 4.6.2 to 4.6.3 - #244
Merged
Merged
Conversation
Bumps [nuxt](https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt) from 4.6.2 to 4.6.3. - [Release notes](https://github.com/nuxt/nuxt/releases) - [Commits](https://github.com/nuxt/nuxt/commits/v4.6.3/packages/nuxt) --- updated-dependencies: - dependency-name: nuxt dependency-version: 4.6.3 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
mbabker
added a commit
that referenced
this pull request
Nov 2, 2026
PR #244 was a Dependabot security update for GHSA-9v7c-q64q-vv33, but it only rewrote the lockfile: nuxt stayed pinned at 4.6.2 in package.json, and because security updates pass minimum-release-age=0, the re-resolve pulled in ansis@4.5.0, which pnpm 11's one-day default then rejected during the deploy's frozen install. - Pin nuxt 4.6.3 and re-resolve the lockfile from its pre-#244 state. - Rename the root package from "nuxt", which collided with the dependency of the same name. - Set minimumReleaseAge explicitly; Dependabot only honors a value configured in pnpm-workspace.yaml, not pnpm's built-in default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps nuxt from 4.6.2 to 4.6.3.
Release notes
Sourced from nuxt's releases.
... (truncated)
Commits
1b09d0cv4.6.3 (#36651)4fd54fftest: listNUXT_B4023as main-only45463f8fix(nitro,nuxt): handle dot segments in request paths57da2aefix(nuxt): apply redirect route rules to page islandsc655a32fix(nuxt): defer app scope cleanup on external navigation (#36713)e2179cefix(nuxt): prevent useCookie CookieStore sync from rewriting with refresh (#3...f818b2efix(nuxt): only return redirects fromnavigateTowhile middleware runs (#36...f5ae355perf(nitro,nuxt,rspack,webpack): bundle esm vue + reuse caches (#36710)6761ca2fix(nuxt): remove purged entries from_asyncData(#36709)8ef5edefix(nuxt): hide RouteLocationRaw from navigateTo's public return type (#36691)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.