Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update nuxt framework to v3.11.1 #41

Merged
merged 1 commit into from
Apr 2, 2024
Merged

fix(deps): update nuxt framework to v3.11.1 #41

merged 1 commit into from
Apr 2, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/kit (source) 3.9.0 -> 3.11.1 age adoption passing confidence
@nuxt/schema (source) 3.9.0 -> 3.11.1 age adoption passing confidence
@nuxt/test-utils 3.9.0 -> 3.12.0 age adoption passing confidence
nuxt (source) 3.9.0 -> 3.11.1 age adoption passing confidence

Release Notes

nuxt/nuxt (@​nuxt/kit)

v3.11.1

Compare Source

3.11.1 is a patch release addressing regressions in v3.11.0.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Ignore console.logs called outside event context (b3ced3d69)
  • schema: Include ofetch in typescript.hoist defaults (#​26316)
  • nuxt: Conditionally use tsx parser (#​26314)
  • nuxt: Correct finish types and add to docs (0d9c63b82)
  • nuxt: Ignore failures to access asyncContext in environments without it (523db1a19)
  • nuxt: Handle failure creating BroadcastChannel (#​26340)
  • nuxt: Don't warn when injecting client-only components (#​26341)
  • nuxt: Prevent losing pages routes on prerender (#​26354)
  • nuxt: Pass undefined name when resolving trailing slash (#​26358)
  • vite: Use ssr result if it exists (#​26356)
📖 Documentation
  • Fix code block formatting for usePreviewMode (#​26303)
  • Fix confusing wording (#​26301)
  • Add note that useId must be used with single root element (401370b3a)
  • Mention <DevOnly> component in api section (#​26029)
  • Note that @nuxt/schema should be used by module authors (#​26190)
  • Add routeNameSplitter example in migration docs (#​25838)
🏡 Chore
  • nuxt: Remove unused code (#​26319)
  • Revert update github/codeql-action action (c72951b06)
🤖 CI
  • Configure npm registry in release workflow (68f7d4df8)
❤️ Contributors

v3.11.0

Compare Source

v3.10.3

Compare Source

3.10.3 is a regularly-scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Respect dedupe option in useFetch (#​25815)
  • nuxt: Bypass browser cache when fetching app build id (#​25813)
  • nuxt: In dev, don't link css files with ?inline query (#​25822)
  • nuxt: Pass external to navigate in custom <NuxtLink> (#​25887)
  • nuxt: Mark internal island components with @__PURE__ (#​25842)
  • nuxt: Use setTimeout before scrolling when navigating (#​25817)
  • nuxt: Add missing type for head in defineNuxtComponent (#​25410)
  • nuxt: Handle undefined paths in resolveTrailingSlashBehavior (ba6a4132b)
  • nuxt: Set to.name to be undefined rather than deleting entirely (4ca1ab7cf)
📖 Documentation
  • Enable more blocks for twoslash (#​25830)
  • Remove .ts extension when adding compiled files (#​25855)
  • Replace callout to new components (#​25897)
  • Fix incorrect wording (#​25902)
🏡 Chore
  • Use nuxt.config to enable pages for docs typecheck (72a2e23cc)
  • Restore environment back to development (3f92cf04d)
  • Unpin vite version 🙈 (d326e054d)
  • nuxt: Use Exclude rather than Omit (3fc4231d3)
🤖 CI
  • Typecheck code samples in docs (#​25777)
  • Update link to stackblitz mcve page (59dd5fd93)
❤️ Contributors

v3.10.2

Compare Source

3.10.2 is a regularly-scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Export refreshCookie (#​25635)
  • nuxt: Allow prefetching urls with query string (#​25658)
  • nuxt: Remove undefined keys in route object (#​25667)
  • vite: Treat .pcss extension as a CSS extension (#​25673)
  • nuxt: Don't check for layout/page with <ClientOnly> (#​25714)
  • vite: Strip query strings for style chunk filenames (#​25764)
  • nuxt: Inline entry styles before component styles (#​25749)
  • vite: Optimise layer dependencies with vite (#​25752)
  • nuxt: Don't add extra baseURL on server useRequestURL (#​25765)
  • schema: Use rootDir, not process.cwd, for modulesDir (#​25766)
  • nuxt: Only warn for useId if attrs were not rendered (#​25770)
  • kit: Don't mutate existing component entry when overriding (#​25786)
📖 Documentation
🏡 Chore
  • schema: Add missing closing code block (#​25641)
❤️ Contributors

v3.10.1

Compare Source

3.10.1 is a regularly-scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Clear route meta build cache when pages change (#​25514)
🩹 Fixes
  • nuxt: Fix syntax error when serializing route meta (#​25515)
  • nuxt: Only request animation frame on client (#​25569)
  • schema: Correctly set value for app.viewTransition (#​25581)
  • nuxt: Correct return type of refresh functions (#​25568)
  • nuxt: Broadcast cookie change in correct format (#​25598)
  • nuxt: Generate typed route declarations when building (#​25593)
  • nuxt: Remove key from useId type signature (#​25614)
  • nuxt: Remove $ from generated id in useId (#​25615)
  • nuxt: Don't set default rel for same-site external links (#​25600)
  • nuxt: Warn if inheritAttrs: false when using useId (#​25616)
  • nuxt: Fetch non-server rendered islands when hydrating (#​25613)
  • nuxt: Don't check page/layout usage when redirecting (#​25628)
💅 Refactors
📖 Documentation
  • Correct typo (#​25523)
  • Add and link to a section on Nuxt context (#​23546)
  • Explain how to set <NuxtLink> defaults in nuxt config (#​25610)
🏡 Chore
  • Use pathe in internal tests (e33cec958)
  • nuxt: Rename nuxt -> nuxtApp internally for consistency (c5d5932f5)
🤖 CI
  • Fix playwright cache (#​25527)
  • Retry flaky test when running in Windows with Webpack (#​25536)
  • Retry flaky test when running in Windows with Webpack (#​25543)
  • Retry flaky test when using Webpack (#​25550)
  • Simplify label PR workflow (#​25579)
❤️ Contributors

v3.10.0

Compare Source

3.10.0 is the next minor/feature release.

👀 Highlights

v3.10 comes quite close on the heels of v3.9, but it's packed with features and fixes. Here are a few highlights.

✨ Experimental shared asyncData when prerendering

When prerendering routes, we can end up refetching the same data over and over again. In Nuxt 2 it was possible to create a 'payload' which could be fetched once and then accessed in every page (and this is of course possible to do manually in Nuxt 3 - see this article).

With #​24894, we are now able to do this automatically for you when prerendering. Your useAsyncData and useFetch calls will be deduplicated and cached between renders of your site.

export defineNuxtConfig({ 
  experimental: { 
    sharedPrerenderData: true
  } 
})

[!IMPORTANT]
It is particularly important to make sure that any unique key of your data is always resolvable to the same data. For example, if you are using useAsyncData to fetch data related to a particular page, you should provide a key that uniquely matches that data. (useFetch should do this automatically.)

👉 See full documentation.

🆔 SSR-safe accessible unique ID creation

We now ship a useId composable for generating SSR-safe unique IDs (#​23368). This allows creating more accessible interfaces in your app. For example:

<script setup>
const emailId = useId()
const passwordId = useId()
</script>

<template>
  <form>
    <label :for="emailId">Email</label>
    <input
      :id="emailId"
      name="email"
      type="email"
    >
    <label :for="passwordId">Password</label>
    <input
      :id="passwordId"
      name="password"
      type="password"
    >
  </form>
</template>
✍️ Extending app/router.options

It's now possible for module authors to inject their own router.options files (#​24922). The new pages:routerOptions hook allows module authors to do things like add custom scrollBehavior or add runtime augmenting of routes.

👉 See full documentation.

Client-side Node.js support

We now support (experimentally) polyfilling key Node.js built-ins (#​25028), just as we already do via Nitro on the server when deploying to non-Node environments.

That means that, within your client-side code, you can import directly from Node built-ins (node: and node imports are supported). However, nothing is globally injected for you, to avoid increasing your bundle size unnecessarily. You can either import them where needed.

import { Buffer } from 'node:buffer'
import process from 'node:process'

Or provide your own polyfill, for example, inside a Nuxt plugin.

// ~/plugins/node.client.ts
import { Buffer } from 'node:buffer'
import process from 'node:process'

globalThis.Buffer = Buffer
globalThis.process = process

export default defineNuxtPlugin({})

This should make life easier for users who are working with libraries without proper browser support. However, because of the risk in increasing your bundle unnecessarily, we would strongly urge users to choose other alternatives if at all possible.

🍪 Better cookie reactivity

We now allow you to opt-in to using the CookieStore. If browser support is present, this will then be used instead of a BroadcastChannel to update useCookie values reactively when the cookies are updated (#​25198).

This also comes paired with a new composable, refreshCookie which allows manually refreshing cookie values, such as after performing a request. See full documentation.

🏥 Detecting anti-patterns

In this release, we've also shipped a range of features to detect potential bugs and performance problems.

  • We now will throw an error if setInterval is used on server (#​25259).
  • We warn (in development only) if data fetch composables are used wrongly (#​25071), such as outside of a plugin or setup context.
  • We warn (in development only) if you are not using <NuxtPage /> but have the vue-router integration enabled (#​25490). (<RouterView /> should not be used on its own.)
🧂 Granular view transitions support

It's now possible to control view transitions support on a per-page basis, using definePageMeta (#​25264).

You need to have experimental view transitions support enabled first:

export default defineNuxtConfig({
  experimental: {
    viewTransition: true
  },
  app: {
    // you can disable them globally if necessary (they are enabled by default)
    viewTransition: false
  }
})

And you can opt in/out granularly:

// ~/pages/index.vue
<script setup lang="ts">
definePageMeta({
  viewTransition: false
})
</script>

Finally, Nuxt will not apply View Transitions if the user's browser matches prefers-reduced-motion: reduce (#​22292). You can set viewTransition: 'always'; it will then be up to you to respect the user's preference.

🏗️ Build-time route metadata

It's now possible to access routing metadata defined in definePageMeta at build-time, allowing modules and hooks to modify and change these values (#​25210).

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  }
})

Please, experiment with this and let us know how it works for you. We hope to improve performance and enable this by default in a future release so modules like @nuxtjs/i18n and others can provide a deeper integration with routing options set in definePageMeta.

📦 Bundler module resolution

With #​24837, we are now opting in to the TypeScript bundler resolution which should more closely resemble the actual way that we resolve subpath imports for modules in Nuxt projects.

'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their package.json.

As part of this, we opened 85 PRs across the ecosystem to test switching the default, and identified and fixed some issues.

If you need to switch off this behaviour, you can do so. However, please consider raising an issue (feel free to tag me in it) in the library or module's repo so it can be resolved at source.

export default defineNuxtConfig({
  future: {
    typescriptBundlerResolution: false
  }
})

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

-->

👉 Changelog

compare changes

🚀 Enhancements
  • nuxt: tryUseNuxtApp composable (#​25031)
  • nuxt: Add experimental sharedPrerenderData option (#​24894)
  • schema: Default to bundler module resolution (#​24837)
  • nuxt: Warn if data fetch composables are used wrongly (#​25071)
  • nuxt: Add pages:routerOptions hook (#​24922)
  • Experimental client-side Node.js compatibility (#​25028)
  • nuxt: Throw error if setInterval is used on server (#​25259)
  • nuxt: refreshCookie + experimental CookieStore support (#​25198)
  • nuxt: Allow controlling view transitions in page meta (#​25264)
  • nuxt: Slow down loading indicator when approaching 100% (#​25119)
  • nuxt: Experimentally extract route metadata at build time (#​25210)
  • nuxt: useId composable (#​23368)
🔥 Performance
  • vite: Avoid endsWith when checking for whitespace (#​24746)
🩹 Fixes
  • nuxt: Disable View Transitions if prefers-reduced-motion (#​22292)
  • nuxt: Add declaration file with correct node16 imports (#​25266)
  • nuxt: Allow omitting fallback in island response (#​25296)
  • schema: Remove defineModel option as it is now stable (#​25306)
  • nuxt: Overwrite island payload instead of merging (#​25299)
  • vite: Pass hidden sourcemap values to vite (#​25329)
  • nuxt: Use named import for lazy components (#​25286)
  • nuxt: Deprecate boolean values for dedupe (#​25334)
  • nuxt: Use default export for raw components (#​25282)
  • nuxt: Handle plugin dependencies with mixed load state (#​25318)
  • nuxt: Preserve instance.attrs in client-only components (#​25381)
  • nuxt: Stop tracking suspense when error hydrating page (#​25389)
  • nuxt: Add router.options files in definite order (#​25397)
  • nuxt: Do not rerun synchronous callOnce callbacks (#​25431)
  • nuxt: Remove dynamic nuxt-client within template code (#​25464)
  • nuxt: Add runtime check to filter plugins in dependsOn (#​25409)
  • nuxt: Improve global/payload error type with NuxtError (#​25398)
  • vite: Extract styles for shared chunks (#​25455)
  • nuxt: Avoid vue-router warning with routeRule redirect (#​25391)
  • nuxt: Improve return type of useRequestEvent (#​25480)
  • nuxt: Match nitro + nuxt useRuntimeConfig signatures (#​25440)
  • nuxt: Prevent initial scroll jump when loading page (#​25483)
  • nuxt: Prioritise later items in pages:routerOptions hook (#​25509)
💅 Refactors
  • nuxt: Remove currentRoute non-ref warning (#​25337)
📖 Documentation
  • Explain how to auto-install git layer deps (#​24250)
  • Fix eslint link (87641c867)
  • Fix typo (#​25326)
  • nuxt: Add @since annotations to exported composables (#​25086)
  • Add emphasis to useAsyncData explanation (#​25392)
  • Add separate docs page for error.vue (#​25320)
  • Add explanation about layout usage in error.vue (#​25396)
  • Use .cjs extension for ecosystem.config (#​25459)
  • Add fuller explanation in routeRules example of swr/isr (#​25436)
  • Warn that island client components don't support slots (#​25454)
  • Updated addPluginTemplate example to add filename property (#​25468)
  • Update link to vercel edge network overview (e01fb7ac3)
  • Remove unnecessary warning on sharedPrerenderData (b0f50bec1)
  • Add more documentation for pages:routerOptions (46b533671)
🏡 Chore
  • Fix typo in warning log (#​25265)
  • nuxt: Warn if NuxtPage is not used when pages enabled (#​25490)
  • Remove extra 'not' in warning message (b96fe1ece)
✅ Tests
🤖 CI
  • Only release from main repo (#​25354)
  • Label pull request based on type in title (#​25404)
  • Wrap PR base label in quotes (#​25432)
  • Update extracting PR labels' names (#​25437)
  • Skip adding PR labels if there are none to add (#​25475)
  • Update changelog with github tags/handles of users (60ab5deb0)
  • Import $fetch (a1fb399eb)
❤️ Contributors

v3.9.3

Compare Source

3.9.3 is a hotfix release to address a regression with CSS in development

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Render stylesheets in dev for non-islands (#​25243)
  • nuxt: Don't set 2x data-island-uid for island children (#​25245)
  • nuxt: Don't share object between raw cookie and cookie ref (#​25255)
📖 Documentation
✅ Tests
  • Add separate suspense test suite (#​22947)
❤️ Contributors

v3.9.2

Compare Source

3.9.2 is a regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Iterate rather than using Object.fromEntries (#​24953)
🩹 Fixes
  • nuxt: Add missing script blocks before island transform (#​25148)
  • kit: Improve types for options in addTemplate (#​25109)
  • nuxt: Apply more import protections for nitro runtime (#​25162)
  • nuxt: Sort pages/ files in en-US locale (#​25195)
  • nuxt: Check for layout after nextTick (#​25197)
  • nuxt: Set nitro log level to match nuxt options (#​25213)
  • nuxt: Await async payload revivers (#​25222)
  • nuxt: Render user-inserted links in island responses (#​25219)
💅 Refactors
  • nuxt: Refactor island response + improve rendering (#​25190)
  • nuxt: Rename to data-island-component (#​25232)
📖 Documentation
  • Correct nuxt image discussion link (#​25090)
  • Fix typo (#​25100)
  • Suggest using <NuxtPage> rather than <RouterView> (#​25106)
  • Fix typo (#​25127)
  • Add demo for view transitions api (3c5ea3457)
  • Remove reference to @nuxt/bridge-edge (3f09ddc31)
  • Remove bridge recommendation only relevant Vue <= 2.6.14 (7bb90f587)
  • Bump nuxt 2 version (98fb2be07)
  • Remove invalid nuxi aliases (#​25209)
  • Add --log-level description (#​25211)
  • Added immediate: false in the appropriate example (#​25224)
  • Mention .global.vue filename for global components (#​25144)
  • Clarify reactivity in composables directory (#​23731)
  • Remove lagon from deployment providers (#​24955)
  • Add eslint setup guide (#​24976)
  • Add information on custom path regexp in definePageMeta (#​25073)
  • Fix addDevServerHandler API (#​25233)
  • Mention installing nuxi for bridge (637f5622d)
🏡 Chore
  • Use v3 branch sandbox in issue template (#​25174)
❤️ Contributors

v3.9.1

Compare Source

3.9.1 is a regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Avoid multiple iterations in useRequestHeaders (#​24853)
  • kit,schema,nuxt: Refactor startsWith to array access (#​24744)
  • nuxt: Use single iteration when normalising routes (#​24946)
  • nuxt: Remove some line breaks when rendering html (#​24888)
🩹 Fixes
  • nuxt: Catch error in NuxtErrorBoundary with ssr: false (#​24896)
  • kit: Show correct error when module can't be loaded (#​24957)
  • nuxt: Deeply watch island props (#​24986)
  • nuxt: Don't show transition on initial page load (#​24935)
  • nuxt: Clone cookie to detect changes within object (#​25007)
  • nuxt: Do not warn about missing layouts on error page (#​25008)
  • nuxt: Ignore plugins typed as any in inferred injections (#​25010)
  • nuxt: Reuse intermediate setup state in <ClientOnly> (#​25009)
  • nuxt: Skip scanning layout/middleware without name (#​25015)
  • nuxt: Wrap universal router currentRoute in Ref (#​25026)
  • nuxt: Stop loading indicator if page keys are the same (#​24931)
💅 Refactors
  • nuxt: Remove old reference to nuxt-config-schema (#​25067)
📖 Documentation
  • Switch features/future docs (f5676fba5)
  • Corrected json syntax in 7.esm.md (#​24937)
  • Specify yarn pnp opt-out for install (#​24923)
  • Capitalise hash for vue-router docs link (#​24948)
  • Add badge for callOnce utility (792cf6713)
  • Warn about hydration issue with URL fragment (#​24961)
  • Mention readValidatedBody and getValidatedQuery (#​24990)
  • Add missing imports for nitro examples (#​25003)
  • Add an example of provide with object syntax plugins (#​24993)
  • Update EOL date for Nuxt 2 (afbc4080b)
  • Add callout for getValidatedRouterParams (#​25057)
  • Warn about ref unwrapping when providing refs from plugin (#​25054)
🏡 Chore
  • Add bullet for adding tests in pr template (2bda817ea)
✅ Tests
❤️ Contributors
nuxt/test-utils (@​nuxt/test-utils)

v3.12.0

Compare Source

compare changes

🚀 Enhancements
  • e2e: Add 'route'/'hydration' options for page.goto() (#​739)
  • e2e: Add playwright runner (#​776)
🩹 Fixes
  • config: Remove nuxt's custom vite logger (eca52f5c)
🏡 Chore
  • Force correct typing for e2e subpath (9fd93a8c)
  • Don't run publish step separately (0078d0bc)
🤖 CI
❤️ Contributors

v3.11.0

Compare Source

compare changes

🚀 Enhancements
  • vitest-environment: Add support for in-source testing (#​651)
🩹 Fixes
  • runtime: Reset modules after nuxt setup runs (#​726)
✅ Tests
  • Add example of mocking vue-router (e293cea1)
  • Add example of mocking nuxt useRoute (fe465193)
❤️ Contributors

v3.10.0

Compare Source

compare changes

🚀 Enhancements
  • e2e: Add cucumber test runner (#​711)
  • e2e: Support env option for startServer (#​640)
🩹 Fixes
  • runtime-utils: Resolve to in RouterLink stub (#​687)
  • Mark afterAll and setup hooks as async (#​702)
  • module: Always append import when mocking (#​701)
🏡 Chore
  • Add required dev deps to app-vitest example (#​712)
  • Pin vue/nuxt versions (00674cd0)
✅ Tests
  • Update config key (25060645)
  • Add example test for nuxt-injected value (#​663)
  • Update to actually use $t (#​675)
🤖 CI
❤️ Contributors

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 these updates again.

  • 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 renovate bot changed the title fix(deps): update nuxt framework to v3.9.1 fix(deps): update nuxt framework to v3.9.2 Jan 16, 2024
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.9.2 fix(deps): update nuxt framework to v3.9.3 Jan 17, 2024
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.9.3 fix(deps): update nuxt framework to v3.10.0 Jan 30, 2024
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.10.0 fix(deps): update nuxt framework to v3.10.1 Feb 5, 2024
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.10.1 fix(deps): update nuxt framework to v3.10.2 Feb 14, 2024
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.10.2 fix(deps): update nuxt framework to v3.10.3 Feb 22, 2024
@renovate renovate bot force-pushed the renovate/nuxt branch 2 times, most recently from 4e4bafd to ed22dad Compare March 17, 2024 09:27
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.10.3 fix(deps): update nuxt framework to v3.11.0 Mar 17, 2024
@renovate renovate bot changed the title fix(deps): update nuxt framework to v3.11.0 fix(deps): update nuxt framework to v3.11.1 Mar 19, 2024
@adenvt adenvt added this pull request to the merge queue Apr 2, 2024
Merged via the queue into main with commit 8de7f09 Apr 2, 2024
3 checks passed
@renovate renovate bot deleted the renovate/nuxt branch April 2, 2024 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@adenvt