Skip to content

chore(deps): update nuxt - #2948

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nuxt
Open

chore(deps): update nuxt#2948
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nuxt

Conversation

@renovate

@renovate renovate Bot commented May 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@nuxt/content (source) 3.12.0 → 3.16.2 age confidence
@nuxt/eslint-plugin (source) 1.15.2 → 1.17.0 age confidence
@nuxt/icon 2.2.1 → 2.5.1 age confidence
@nuxt/kit (source) 4.3.1 → 4.6.2 age confidence
@nuxt/test-utils 4.0.0 → 4.3.4 age confidence
@nuxt/ui (source) 4.5.1 → 4.12.0 age confidence
nuxt (source) 4.3.1 → 4.6.2 age confidence
nuxt-auth-utils 0.5.29 → 0.5.32 age confidence
ufo 1.6.3 → 1.6.4 age confidence
unstorage 1.17.4 → 1.17.6 age confidence
vite (source) 7.3.1 → 7.3.7 age confidence
zod (source) 4.3.6 → 4.6.7 age confidence

Release Notes

nuxt/content (@​nuxt/content)

v3.16.2

Compare Source

Bug Fixes
Performance Improvements

v3.16.1

Compare Source

Features
  • add content.llms option to disable the nuxt-llms integration (#​3843) (656a5ce)
Bug Fixes

v3.16.0

Compare Source

Bug Fixes
  • avoid install prompt in non-interactive environments (#​3833) (2d0e84b)
  • ContentRenderer: keep async component identity stable across re-resolves (#​3835) (dcf86e6)
  • improve generated git cache key (#​3839) (d1e353e)
  • module: keep content templates when building with _prepare (#​3837) (e390c3b)
  • nuxthub: handle object form of hub.db (#​3822) (8841abc)
  • query: tolerate trailing slashes in path-based lookups (#​3838) (220d392)
  • runtime: use dynamic import for #content/adapter to prevent prerender failure (#​3830) (400390a)
  • use UTC getters in formatDate/formatDateTime to prevent timezone drift (#​3782) (9f1f89a)

v3.15.2

Compare Source

Bug Fixes
  • dev: ignore temporary files in content source paths (#​3784) (a019e70)
  • security: reject SQL function calls in query WHERE clauses (#​3819) (847d523)

v3.15.1

Compare Source

Bug Fixes

v3.15.0

Compare Source

Features
Bug Fixes
  • content: support validator detection with pnpm enableGlobalVirtualStore (#​3791) (6b2720b)
  • hmr: update all matching collections when a file changes (#​3802) (06f8edb)
  • search: softer heading-level boost curve and tuned defaults (#​3801) (00d25a5)
  • vercel: use tmp directory to clone contents (#​3810) (793d59a)

v3.14.0

Compare Source

Features
Bug Fixes
  • docs: update Nuxt version from 3 to 4 in template features (#​3780) (1f24029)
  • path-meta: slugify function did not pass to transformer (#​3794) (778d7db)
  • preview: skip collections without source in preview template (#​3771) (8aabefd)

v3.13.0

Compare Source

Bug Fixes
  • get mdc configs by calling mdc:configSources hook (#​3736) (57f5552)
  • preview: move formatDate/formatDateTime into runtime subtree (#​3749) (4a76b2a)
nuxt/eslint (@​nuxt/eslint-plugin)

v1.17.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.16.0

Compare Source

   🚀 Features
    View changes on GitHub
nuxt/icon (@​nuxt/icon)

v2.5.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.5.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.4.1

Compare Source

No significant changes

    View changes on GitHub

v2.3.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.3.0

Compare Source

   🚀 Features
    View changes on GitHub

v2.2.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.2.4

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v2.2.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
nuxt/nuxt (@​nuxt/kit)

v4.6.2

Compare Source

v4.6.2 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • nitro: apply useHeadSafe rules to server island head (493565e99)
  • nitro-server: read router params from the path h3 matched (010f6b43d)
  • nitro: match server route rules case-insensitively unless routing is sensitive (f6cfee52c)
  • nuxt: resolve rooted paths through the URL parser (#​36617)
  • nuxt: resolve empty route types in shared context (#​36576)
  • nitro: preserve server tsconfig with relocated build dir (#​36494)
  • nuxt: fix scroll offset for IDs starting with numbers (#​36524)
  • kit: do not exclude module directories with a dot in their name from app tsconfig (#​36331)
  • nuxt: detect vapor slots with rawVaporSlotKey from vue (#​36614)
  • nuxt: keep middleware layout when restoring deferred prerendered route (#​36560)
  • schema: provide default value for experimental.typescriptPlugin (#​36561)
  • vite: only replay compile error overlays to newly loaded pages (#​36611)
  • nuxt: re-export AnyFetchPath for emitted server route types (#​36610)
  • vite: warm up the dev ssr entry from a nitro plugin (#​36615)
  • nitro: avoid unused h3 imports in nuxt/server runtime (#​36609)
  • vite-server: scope asset url helpers to the build (#​36591)
  • nuxt: resolve nuxt/app to the app's runtime (#​36587)
  • kit: lowercase filename-derived handler method on nitro v2 (#​36567)
  • nuxt,nitro: normalise string/array appMiddleware (#​36565)
  • nitro: pass response headers to render:response listeners (#​36583)
  • vite: resolve inlined vue to its bundler build in dev (#​36569)
  • nuxt: don't start a page transition with no page to leave (#​36535)
  • nuxt: preserve error state on aborted or cancelled navigation (#​36546)
  • vite,nitro: link null-byte virtual css through /@id/ in dev (#​36549)
  • kit: resolve module dependencies from the declaring module (#​36542)
  • nitro: only disable h3 + nitro presets when nitroAutoImports is off (#​36548)
  • nitro,vite: don't access unspecified dependencies (#​36541)
  • nitro: don't inline deps under absolute transpile dirs (#​36540)
  • vite-server: respect spa loading template location (#​36536)
💅 Refactors
  • webpack,rspack: inline friendly errors plugin (#​36568)
📖 Documentation
  • remove DeepWiki badge (#​36616)
  • rename H(TTP) to HTTP (#​36559)
  • mention proxy route rule (4a529be68)
  • reference definePlugin and defineNitroPlugin in server plugin tip (64b8e0334)
  • open a PR to list a module (e551df267)
  • clarify testing environments, runners, and config (#​32963)
  • align spa loading template references (#​36552)
  • explain how to disable iOS Safari phone number detection (#​36539)
  • fix outdated internal links (#​36550)
  • explain how to restore nitro auto-imports with compat v5 (7499a445b)
  • add spa-loading-template documentation (#​36537)
🏡 Chore
✅ Tests
  • wait for scroll to settle in route-scroll e2e (ca784deb7)
🤖 CI
  • comment nuxt.com preview links on docs pull requests (#​36594)
  • regenerate kit inlinedDependencies in autofix (4b6da3a29)
  • remove docs deploy triggers (917bdf218)
🎉 New Contributors
❤️ Contributors

v4.6.1

Compare Source

v4.6.1 is the next patch release.

👉 Changelog

compare changes

🔥 Performance
  • nitro: build the portable event's web view on first access (cffb182d6)
🩹 Fixes
  • vite: match vite 8.1+ optimizer messages for deps hint (#​36525)
  • nuxt: accept any baseURL when fetch response type is named (#​36523)
  • nitro: resolve nitropack/types declarations under nodenext (242e1971e)
  • nuxt: allow false in setPageLayout types (#​36506)
  • nuxt: align Serialize object types with JSON (#​36503)
  • vite: don't abort dep scan on virtual imports in installed packages (#​36477)
  • nuxt: update publishConfig config export extension (64fa191cb)
  • kit: install the package a missing subpath belongs to (#​36507)
  • vite-server: use the configured outDir as the public directory for non-ssr environment (#​36501)
  • kit,nitro: match dev handler paths on both nitro majors (#​36515)
  • nuxt: preserve onServerPrefetch for useId hydration (#​36430)
  • vite-server: include the request in dev error reports (#​36489)
  • nitro: register each dev server handler once (#​36493)
  • nitro: pass RequestEvent to nuxt dev server handlers (e6beceea2)
  • nuxt: type the global $fetch with nuxt's TypedFetch (#​36492)
  • vite-server: work with deploy target plugins in dev (#​36491)
  • schema: ignore .wrangler directory (#​36487)
  • vite-server: pass the path to the error page render (#​36488)
  • nuxt,vite: disable dev error broadcast if BroadcastChannel throws (#​36480)
  • kit: align semantic version regexp with nightly version format (#​36479)
  • nuxt: export types reachable from async data composables (#​36478)
  • vite: detect enclosing string delimiter in inline style urls (#​36476)
  • schema: type the nuxt dev server handler variant (452052793)
  • nitro: inline nuxt runtime when resolved to windows paths (21657c6fc)
  • nitro: resolve unhead from nuxt in server bundle (dc1e2d6e6)
💅 Refactors
  • kit: use package-manager-detector workspace + deno handling (1563a6d25)
📖 Documentation
  • document dev server handlers and nuxt/server scope (7c36a1352)
  • fix nightly examples (#​36486)
🏡 Chore
✅ Tests
  • resolve temporary fixture paths on macos (30742865c)
  • update test expectation (1f22a114d)
🤖 CI
🎉 New Contributors
❤️ Contributors

v4.6.0

Compare Source

v4.6.0 is the next minor release.

📣 Some news

🖥️ Nuxt CLI v4

Alongside the release of Nuxt v4.6, today also brings a new major release of the Nuxt CLI: @nuxt/cli v4. It ships as a dependency of nuxt, so you'll get it automatically when you upgrade.

Most of what's new is in nuxt dev:

  • an interactive terminal UI, showing URLs, startup progress and keyboard shortcuts, with panels to dive into error logs, routes, network requests and more
  • the dev server gives you more info, such as why it reloaded or restarted, which nuxt.config keys changed, where the time went during a slow start or build, and how long each module took to set up
  • a CLI-level error channel rendered with my-bad (see below), powering things like automatically reloading when a syntax error in nuxt.config.ts is fixed
  • a lock file in .nuxt/, which lets a second nuxt dev (say, one started by an agent) take over or defer to the one you started, and powers new nuxt curl and nuxt task commands that talk to the running server

There's also a new nuxt docs "<query>" search, and nuxt preview --takeover can replace a running preview server. And in general nuxt/cli is a lot smaller and starts a lot faster:

v3.37 v4.0
@nuxt/cli install size 13.1 MB 3.5 MB -73%
@nuxt/cli dependencies 70 31 -56%
nuxt dev: first paint 330 ms 50 ms 6.6x faster
nuxt dev: port bound 338 ms 104 ms 3.2x faster
nuxt dev: memory at rest (Linux) 630 MB 440 MB -30%
nuxt-dev

Although this is a major version, none of the changes should be breaking for Nuxt v4 users: we require Node.js v22.21+, v24.11+ or v26+, we drop nuxt init and only support npm create nuxt@latest, and Nuxt 2 and @nuxt/bridge are no longer supported.

👉 Check out the full Nuxt CLI v4 release notes for everything that's changed.

💡 A server-agnostic Nuxt

The biggest thing about this release is our move towards making Nuxt server-agnostic.

I feel that freedom of choice is very much a fundamental value of the web, and one that unites the whole Nuxt team.

You can use pages/ (with vue-router) or not. You can use Vite, webpack or Rspack to bundle your code. You can pick from dozens of providers to deploy to, pick any image or font provider, choose any database adapter. In every case, the framework is the same.

The server side was different. #app composables imported h3 types, server code imported from h3 and nitropack, and every module that touched the server was tied to whichever major version of those packages Nuxt happened to depend on.

This has become particularly clear as we have been upgrading to new majors of h3 and nitro, which ship breaking changes with a cascading effect throughout the whole ecosystem.

👉 This release changes that.

Alongside explicitly defining our public API in nuxt/kit (which now does not refer to external packages), Nuxt now specifies our own types for the request event, route rules and typed $fetch, and we expose an import surface (nuxt/server) for the server utilities that will be needed by most apps.

This is the culmination of work we started almost a year ago, making it possible to use any server builder with Nuxt, not just Nitro (#​33462).

Of course, under the hood, nuxt/server is still powered by Nitro by default - though we are also announcing a second, experimental implementation, @nuxt/vite-server, which allows pure-Vite server builds using the Vite Environment API.

[!IMPORTANT]
We believe that Nitro is still the right choice for almost everyone.

🌟 We see a number of key benefits for nuxt/server.

  1. it smooths the upgrade to Nuxt 5, which moves to Nitro v3 and h3 v2. Server code written against nuxt/server on 4.6 runs unchanged there, so a module can ship one file for both.
  2. it decouples Nuxt from the Nitro release cycle. Because we 'own' the API, we can adapt to breaking changes in Nitro or h3 without requiring a future major - and we can release Nuxt majors without having to wait for upstream releases.
  3. it makes Nuxt's code more maintainable. It helps us preserve the separation of concerns between our API - /app and /server - and the bundler + server that you ultimately want to build your app.

... and there are a number of other benefits too, from a single type surface to being able to iterate more quickly on features.

Finally, I want to say a special thank-you to @​pi0, whose relentless focus on server agnosticism and work on h3, Nitro and web-standard server primitives over the last few years is what makes a portable RequestEvent possible at all. Thank you, Pooya. ❤️

Almost every feature in this release is already in the Nuxt 5 branch, and most of the remaining Nuxt 5 defaults can be tested today with future.compatibilityVersion: 5 (more details below!).

[!TIP]
Nuxt 3 reached end-of-life on July 31, 2026, so there is no 3.x release alongside this one. If you're still on v3, the upgrade guide is waiting for you.

👀 Highlights

🤷 If you've read this far I'm afraid I have bad news for you: there's a lot more still to say! Nuxt 4.6 is one of our biggest minor releases, with over 420 commits since v4.5.2.

... so, you might want to grab a coffee! ☕️

🧩 nuxt/server

It has been asked for for a long time, and it now exists (#​36275)!

nuxt/server is a new import source for server code: handlers, middleware and utilities - a complement to nuxt/app. Where nuxt/app is for the part of your application that also runs in the browser, nuxt/server is for the part that only runs on the server.

import { defineEventHandler, getQuery } from 'nuxt/server'

export default defineEventHandler((event) => {
  const { name } = getQuery<{ name?: string }>(event)
  return { message: `Hello, ${name ?? 'world'}!` }
})

The utilities use web standards and are typed against a portable RequestEvent:

event.req         // Request
event.url         // URL
event.res         // { status, statusText, headers }
event.res.headers // Headers
event.context     // per-request context

Under @nuxt/nitro-server they are backed by Nitro and h3, but you never import from either.

So the same handler runs under Nitro v2, Nitro v3 or @nuxt/vite-server, and a module that imports from nuxt/server doesn't need a peer dependency on h3 or nitropack.

We think this will make a big difference in smoothing out the upgrade to Nuxt v5 and Nitro v3.

There is a typing benefit too. We no longer hoist h3 or Nitro types into your app to type useRequestEvent, $fetch or route rules, which removes a source of type conflicts when versions differ (#​36212, #​36214, #​36293).

The surface is small, and covers what published modules and user code typically need: defineEventHandler, createError/isNuxtError, request URL, headers, query, body (plain and validated with any Standard Schema library or a function), cookies, redirects, response status, getRouterParam(s), getRequestIP, handleCors, getRouteRules, useRuntimeConfig, useAppConfig and sessions.

import { defineEventHandler, readValidatedBody } from 'nuxt/server'
import { z } from 'zod'

export default defineEventHandler(async (event) => {
  const user = await readValidatedBody(event, z.object({ name: z.string() }))
  return { created: user.name }
})

We encourage you to use web APIs (event.req.headers, for example), or raise an issue if there's functionality you're missing from nuxt/server 🙏

If you do need to step outside nuxt/server for a particular handler, don't worry! Nothing has been taken away: import defineEventHandler and the helpers you need from h3 or nitropack/runtime as before, and that handler works exactly as it did on Nuxt 4.5.

import { defineEventHandler, readMultipartFormData } from 'h3'

export default defineEventHandler(async (event) => {
  const parts = await readMultipartFormData(event)
  return { received: parts?.length ?? 0 }
})

[!IMPORTANT]
On Nuxt 4, the auto-imported defineEventHandler, getQuery, readBody and the rest are still h3's own helpers, which take a different shape of event. Import from nuxt/server explicitly, including defineEventHandler to use the new server runtime. If you mix the two, you'll see a NUXT_E8012 error which should tell you which import to change.

A few helpers also behave differently from their h3 v1 namesakes: sendRedirect returns the response rather than sending it, createError takes status and statusText, and response headers are set through event.res.headers. The upgrade guide has a table of the differences.

Nothing in this release requires a migration. But if you have server code you'd like to make portable ahead of Nuxt 5, this is the best way.

👉 Read the server imports guide.

🔐 appSecret and sessions

Nuxt now has a root application secret: runtimeConfig.appSecret, set with NUXT_APP_SECRET (#​35874, thanks to @​onmax). Modules and server features derive purpose-specific secrets from it with deriveSecret(purpose), so NUXT_APP_SECRET is the only secret you need to configure.

openssl rand -base64 32

In development Nuxt generates and persists one if none is configured (and warns the first time a derived secret is used). Builds never generate one.

The first thing to use it is a set of session helpers in nuxt/server (#​36358). Sessions are sealed into a cookie with iron, so there's no server-side storage to configure:

import { defineEventHandler, useSession } from 'nuxt/server'

export default defineEventHandler(async (event) => {
  const session = await useSession<{ visits: number }>(event)
  await session.update(data => ({ visits: (data.visits ?? 0) + 1 }))
  return { visits: session.data.visits }
})

[!NOTE]
As a reminder, runtime config keys prefixed with app (runtimeConfig.app, runtimeConfig.appSecret) are reserved for Nuxt.

🎯 Typed $fetch, rebuilt

$fetch and useFetch have been typed from your server routes for a long time. But the types were derived from Nitro's InternalApi interface, and past a few hundred routes they hit TypeScript's instantiation limit with the familiar TS2589: Type instantiation is excessively deep and possibly infinite.

We've rebuilt typed fetch on top of fetchdts (#​36238). Nuxt compiles your server routes into a route tree with an exact-match table for static paths and accessors specialised to your route set. Resolution cost now scales with call sites, not with route count:

routes before after
100 1,397,361 instantiations / 0.77s 51,558 / 0.26s
300 5,774,425 / 3.49s (TS2589) 51,558 / 0.16s
1000 12,831,467 / 7.44s (TS2589) 51,558 / 0.20s
3000 (200 call sites) 71,875,148 / 53.63s (TS2589) 101,678 / 0.62s

Peak memory for the same runs dropped from 946 MB to 140 MB. 🔥

Plus, the route set also carries the body, query and headers a handler validates, so calls are checked more tightly than before:

// server/api/users.post.ts validates { title: string, count: number }
await $fetch('/api/users', { method: 'post', body: { title: 'a', count: 1 } })
await $fetch('/api/users', { method: 'post', body: { title: 'a', count: 'no' } })
//                                                                ^ not assignable to number
await $fetch('/api/users', { method: 'post' })
//           ^ body is required

On Nuxt 4 this is opt-in, because there are small changes to type inference, and hand-written ServerRoutes augmentations need a small rewrite. It is the default in Nuxt 5.

export default defineNuxtConfig({
  experimental: {
    routeTypedFetch: true,
  },
})

There's also a new experimental.strictRouteTypes option to reject calls to paths that don't exist (otherwise these just return unknown), and an 'isomorphic' mode that types your pages as GET routes too if you want to be able to $fetch from the Vue renderer with type safety.

👉 Read more in the experimental features docs.

🐛 Better errors in development with my-bad

Server-side errors in development used to look like this:

ReferenceError: foo is not defined
    at Object.<anonymous> (/_nuxt/app/pages/index.vue:1:1)

There was no source position or code frame, and the Youch iframe we rendered could not show you the frame in your own source either. Both are now fixed (#​36258, nuxt/cli#1518).

Dev SSR stack traces are now mapped before anything reads the error, and the Youch overlay has been replaced with my-bad. It renders into your app's own error page as an overlay (or as a standalone page when the app can't render one), with the mapped stack trace and a code frame from your source, and the same report is printed in your terminal. We are still working with @​atinux, @​HugoRCD and @​antfu to make these pages nicer still.

my-bad-ssr-expanded-dark my-bad-ssr-copymenu-dark

With Nuxt CLI v4, there is a single live error channel at the CLI level. It survives worker restarts, so (for example) a syntax error in nuxt.config.ts will live-reload the page once you fix it. Each error is rendered once rather than at every layer it passes through, and the same channel streams build progress and app logs to the dev panel.

🎨 A new loading screen, 404 and error pages

@​HugoRCD has redrawn the loading screen you see while the dev server starts. It is now a WebGL2 particle field that traces a mountain range behind the Nuxt lockup (#​36178), using a single shader and a single draw call. Without WebGL2 it falls back to the static lockup, and with prefers-reduced-motion the animation stops. Try hovering over it. 🏔️

Hugo also gave the built-in 404 and error pages a neutral palette and lighter type (#​36255), and @​MirkoJa added a back button to the 404 page (#​35688).

404-page-dark
⚡️ Vue Vapor support

Nuxt now supports Vue 3.6's Vapor Mode in interop mode (#​35759). Your app root stays on the virtual DOM, and you can opt individual components or pages into Vapor by adding the vapor attribute to <script setup>:

export default defineNuxtConfig({
  vue: {
    vapor: true,
  },
})
<script setup vapor lang="ts">
const count = ref(0)
</script>

<template>
  <button @click="count++">
    count is {{ count }}
  </button>
</template>

Routing, useAsyncData, layouts and most built-in components keep working unchanged. Along the way we made the auto-import loader, useAsyncData, definePageMeta and slot inspection Vapor-aware, and we now have a Vapor test suite so we can track what's supported.

[!NOTE]
This requires Vue ^3.6.0-rc.2 or newer. See the known limitations and try it in a fresh project first.

🧩 Addons for useFetch and useAsyncData

@​cernymatej has added an addons option to the createUseFetch and createUseAsyncData factories (#​35797). An addon can declare custom call-site options, adjust the merged options, wrap the handler with middleware, and extend what the composable returns, and it can be reused across as many custom instances as you like.

const refreshOnFocus = defineUseFetchAddon({
  setup: (options: UseFetchAddonOptions<{ refreshOnFocus?: boolean }>) => {
    if (import.meta.server || !options.refreshOnFocus) { return }

    return (asyncData) => {
      const focused = useWindowFocus()
      watch(focused, focused => focused && asyncData.refresh())
      return { focused }
    }
  },
})

export const useApiFetch = createUseFetch({ baseURL: '/api', addons: [refreshOnFocus] })
<script setup lang="ts">


> [!IMPORTANT]
> ✂ PR body was truncated to here.


</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - "on the 2nd through 5th day of the month"
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/JabRef/JabRefOnline).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNTkuMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE4MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

@renovate
renovate Bot enabled auto-merge (squash) May 3, 2026 18:15
@renovate
renovate Bot force-pushed the renovate/nuxt branch 3 times, most recently from 6ceface to 8175cfc Compare May 5, 2026 06:41
@github-actions

github-actions Bot commented May 5, 2026 •
edited
Loading

Copy link
Copy Markdown

Deployed 4f4a1d2 to https://gentle-forest-03418aa03-2948.westeurope.3.azurestaticapps.net

@renovate
renovate Bot force-pushed the renovate/nuxt branch 13 times, most recently from cea1b20 to fdb2d25 Compare May 12, 2026 09:59
@renovate
renovate Bot force-pushed the renovate/nuxt branch 2 times, most recently from 69d3017 to 622e23d Compare May 18, 2026 11:15
@renovate
renovate Bot force-pushed the renovate/nuxt branch 3 times, most recently from 4cfc2a8 to bdbb631 Compare May 24, 2026 17:54
@renovate
renovate Bot force-pushed the renovate/nuxt branch 4 times, most recently from c6d6fd5 to d24a06d Compare June 4, 2026 15:08
@renovate
renovate Bot force-pushed the renovate/nuxt branch 3 times, most recently from cfb1f25 to 01b1b9f Compare June 11, 2026 18:52
@renovate
renovate Bot force-pushed the renovate/nuxt branch 4 times, most recently from 409fb61 to e6295ea Compare July 31, 2026 05:14
@renovate
renovate Bot force-pushed the renovate/nuxt branch 3 times, most recently from e26e3cf to 5baa29a Compare August 4, 2026 12:50
@renovate
renovate Bot force-pushed the renovate/nuxt branch from 5baa29a to d81282c Compare August 6, 2026 19:49
@renovate
renovate Bot force-pushed the renovate/nuxt branch 9 times, most recently from 334575d to a009d5c Compare August 13, 2026 09:40
@renovate
renovate Bot force-pushed the renovate/nuxt branch 7 times, most recently from 2048fda to 258964f Compare September 1, 2026 01:30
@renovate
renovate Bot force-pushed the renovate/nuxt branch 2 times, most recently from 0fad1ea to a4bac13 Compare September 2, 2026 06:37

This branch has not been deployed

No deployments
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.

0 participants