[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[x] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
📚 Description
Currently supporting multi-support is done through explicit build-time routes or using a middleware if they're chunked. This blocks us from generating runtime sitemaps when not chunking, as the paths are registered. This is an issue for multi-tenancy apps and is blocking https://github.com/nuxt-modules/sitemap/issues/265.
The paths change from /{name}-sitemap.xml to /__sitemap__/{name}.xml and are handled by Nitro named routes.
:warning: This is a breaking change if users have registered the multi-sitemap paths in Google Search Console, users should update these when upgrading.
[x] Add redirects from old sitemap to new for v6 major
🔗 Linked issue
n/a
❓ Type of change
📚 Description
Currently supporting multi-support is done through explicit build-time routes or using a middleware if they're chunked. This blocks us from generating runtime sitemaps when not chunking, as the paths are registered. This is an issue for multi-tenancy apps and is blocking https://github.com/nuxt-modules/sitemap/issues/265.
The paths change from
/{name}-sitemap.xmlto/__sitemap__/{name}.xmland are handled by Nitro named routes.:warning: This is a breaking change if users have registered the multi-sitemap paths in Google Search Console, users should update these when upgrading.