chore(deps): bump the prod-deps group with 6 updates

[dependabot]

Updates the requirements on @astrojs/tailwind, @sentry/astro, astro, caniuse-lite, flowbite and tailwindcss to permit the latest version.
Updates @astrojs/tailwind from 5.1.5 to 6.0.0

Release notes

Sourced from @​astrojs/tailwind's releases.

@​astrojs/tailwind@​6.0.0

Major Changes

• #13049 2ed4bd9 Thanks @​florian-lefebvre! - Deprecates the integration

  Tailwind CSS now offers a Vite plugin which is the preferred way to use Tailwind 4 in Astro. Please uninstall @astrojs/tailwind and follow the Tailwind documentation for manual installation.

  This updated major version is only provided as a convenience for existing projects until they are able to migrate to the new plugin. It offers no additional functionality and is no longer recommended, but may continue to be used in your projects until it is removed entirely.

Changelog

Sourced from @​astrojs/tailwind's changelog.

6.0.0

Major Changes

• #13049 2ed4bd9 Thanks @​florian-lefebvre! - Deprecates the integration

  Tailwind CSS now offers a Vite plugin which is the preferred way to use Tailwind 4 in Astro. Please uninstall @astrojs/tailwind and follow the Tailwind documentation for manual installation.

  This updated major version is only provided as a convenience for existing projects until they are able to migrate to the new plugin. It offers no additional functionality and is no longer recommended, but may continue to be used in your projects until it is removed entirely.

Commits

• f6b7839 [ci] release (#13086)
• 61ef2d9 chore: upgrade Vite and update tests (#13076)
• See full diff in compare view

Updates @sentry/astro to 8.52.1

Release notes

Sourced from @​sentry/astro's releases.

8.52.1

• fix(v8/nextjs): Fix nextjs build warning (#15226)
• ref(v8/browser): Add protocol attributes to resource spans #15224
• ref(v8/core): Don't set this.name to new.target.prototype.constructor.name (#15222)

Work in this release was contributed by @​Zen-cronic. Thank you for your contribution!

Bundle size 📦

Path	Size
@​sentry/browser	23.3 KB
@​sentry/browser - with treeshaking flags	23.17 KB
@​sentry/browser (incl. Tracing)	35.9 KB
@​sentry/browser (incl. Tracing, Replay)	73.27 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.71 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	77.57 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	89.5 KB
@​sentry/browser (incl. Feedback)	39.51 KB
@​sentry/browser (incl. sendFeedback)	27.91 KB
@​sentry/browser (incl. FeedbackAsync)	32.71 KB
@​sentry/react	25.98 KB
@​sentry/react (incl. Tracing)	38.71 KB
@​sentry/vue	27.58 KB
@​sentry/vue (incl. Tracing)	37.75 KB
@​sentry/svelte	23.46 KB
CDN Bundle	24.49 KB
CDN Bundle (incl. Tracing)	37.6 KB
CDN Bundle (incl. Tracing, Replay)	72.9 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.23 KB
CDN Bundle - uncompressed	71.92 KB
CDN Bundle (incl. Tracing) - uncompressed	111.52 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	225.78 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	238.88 KB
@​sentry/nextjs (client)	38.96 KB
@​sentry/sveltekit (client)	36.4 KB
@​sentry/node	162.84 KB
@​sentry/node - without tracing	99.15 KB
@​sentry/aws-serverless	126.67 KB

Changelog

Sourced from @​sentry/astro's changelog.

8.52.1

• fix(v8/nextjs): Fix nextjs build warning (#15226)
• ref(v8/browser): Add protocol attributes to resource spans #15224
• ref(v8/core): Don't set this.name to new.target.prototype.constructor.name (#15222)

Work in this release was contributed by @​Zen-cronic. Thank you for your contribution!

8.52.0

Important Changes

• feat(solidstart): Add withSentry wrapper for SolidStart config (#15135)

To enable the SolidStart SDK, wrap your SolidStart Config with withSentry. The sentrySolidStartVite plugin is now automatically added by withSentry and you can pass the Sentry build-time options like this:

import { defineConfig } from '@solidjs/start/config';
import { withSentry } from '@sentry/solidstart';
export default defineConfig(
withSentry(
{
/* Your SolidStart config options... */
},
{
// Options for setting up source maps
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
authToken: process.env.SENTRY_AUTH_TOKEN,
},
),
);

With the withSentry wrapper, the Sentry server config should not be added to the public directory anymore. Add the Sentry server config in src/instrument.server.ts. Then, the server config will be placed inside the server build output as instrument.server.mjs.

Now, there are two options to set up the SDK:

1. (recommended) Provide an --import CLI flag to the start command like this (path depends on your server setup): node --import ./.output/server/instrument.server.mjs .output/server/index.mjs
2. Add autoInjectServerSentry: 'top-level-import' and the Sentry config will be imported at the top of the server entry (comes with tracing limitations)

   withSentry(
     {
       /* Your SolidStart config options... */
     },
     {

... (truncated)

Commits

• 42011b5 release: 8.52.1
• 0114ba4 meta: Update changelog for 8.52.1 (#15230)
• 6152ef5 ref(v8/browser): Add protocol attributes to resource spans (#15224)
• a0470da ref(v8/core): Don't set this.name to `new.target.prototype.constructor.name...
• 4574acc test(v8): Fix nextjs build warning (#15226)
• 0cfcd6f ci(v8): Pin node-integration-test version to 18.20.5 (#15221)
• 42969d7 Merge branch 'release/8.52.0' into v8
• bbafacb release: 8.52.0
• a6f7300 meta(changelog): Update CHANGELOG for 8.52.0 (#15177)
• cb6aca7 fix(v8/core): Pass module into loadModule (#15139) (#15166)
• Additional commits viewable in compare view

Updates astro to 5.2.1

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

• #13095 740eb60 Thanks @​ascorbic! - Fixes a bug that caused some dev server asset requests to return 404 when trailingSlash was set to "always"

Changelog

Sourced from astro's changelog.

5.2.1

Patch Changes

• #13095 740eb60 Thanks @​ascorbic! - Fixes a bug that caused some dev server asset requests to return 404 when trailingSlash was set to "always"

5.2.0

Minor Changes

• #12994 5361755 Thanks @​ascorbic! - Redirects trailing slashes for on-demand pages

  When the trailingSlash option is set to always or never, on-demand rendered pages will now redirect to the correct URL when the trailing slash doesn't match the configuration option. This was previously the case for static pages, but now works for on-demand pages as well.

  Now, it doesn't matter whether your visitor navigates to /about/, /about, or even /about///. In production, they'll always end up on the correct page. For GET requests, the redirect will be a 301 (permanent) redirect, and for all other request methods, it will be a 308 (permanent, and preserve the request method) redirect.

  In development, you'll see a helpful 404 page to alert you of a trailing slash mismatch so you can troubleshoot routes.

• #12979 e621712 Thanks @​ematipico! - Adds support for redirecting to external sites with the redirects configuration option.

  Now, you can redirect routes either internally to another path or externally by providing a URL beginning with http or https:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  export default defineConfig({
  redirects: {
  '/blog': 'https://example.com/blog',
  '/news': {
  status: 302,
  destination: 'https://example.com/news',
  },
  },
  });

• #13084 0f3be31 Thanks @​ematipico! - Adds a new experimental virtual module astro:config that exposes a type-safe subset of your astro.config.mjs configuration

  The virtual module exposes two sub-paths for controlled access to your configuration:

  • astro:config/client: exposes config information that is safe to expose to the client.
  • astro:config/server: exposes additional information that is safe to expose to the server, such as file/dir paths.

  To enable this new virtual module, add the experimental.serializeManifest feature flag to your Astro config:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
  export default defineConfig({

... (truncated)

Commits

• 3b10b97 [ci] release (#13096)
• 23e631c [ci] format
• 740eb60 fix: exclude Vite requests from trailing slash handling (#13095)
• f6b7839 [ci] release (#13086)
• 0f10384 [ci] format
• 037495d feat: content layer typings (#12666)
• 23881e7 docs: update integrations JSDoc to replace Tailwind integration (#13089)
• 61ef2d9 chore: upgrade Vite and update tests (#13076)
• 1c42fb4 [ci] format
• c3ed9ee fix: docs and types (#13087)
• Additional commits viewable in compare view

Updates caniuse-lite to 1.0.30001696

Commits

• 005e74e Update caniuse-db 1.0.30001696
• See full diff in compare view

Updates flowbite from 2.5.2 to 3.0.0

Release notes

Sourced from flowbite's releases.

v3.0.0

• upgrade to Tailwind v4
• refactor and adapt the Flowbite plugin and UI components to the new deprecated changes from Tailwind v4

Commits

• a10d2d6 refactor(plugin): use CSS variables for colors instead of hex overriding
• ad0a91e docs(quickstart): slightly improve wording of the docs
• 821eb37 refactor(general): remove safelist and update example shortcode css file
• ebd0470 push lock file
• 724fcdf update docs to main css
• 85abf78 docs(grammar): fix
• a696499 chore(tailwind cli): v4.0
• 8165fe5 readme(v4): guide
• d183a0a chore(tailwind): stable v4
• 6cb4657 docs(v4): guide finish
• Additional commits viewable in compare view

Updates tailwindcss from 3.4.17 to 4.0.1

Release notes

Sourced from tailwindcss's releases.

v4.0.1

Added

• Include :open pseudo-class in existing open variant (#15349)

Fixed

• Remove invalid min-w/h-none utilities (#15845)
• Discard CSS variable shorthand utilities that don't use valid CSS variables (#15738)
• Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#15921)
• Ensure font-size utilities with unknown modifier don't generate CSS (#15921)
• Don’t suggest font weight utilities more than once (#15857)
• Suggest container query variants (#15857)
• Disable bare value suggestions when not using the --spacing variable (#15857)
• Ensure suggested classes are properly sorted (#15857)
• Don’t look at .gitignore files outside initialized repos (#15941)
• Find utilities when using the Svelte class shorthand syntax across multiple lines (#15974)
• Find utilities when using the Angular class shorthand syntax (#15974)
• Find utilities when using functions inside arrays (#15974)
• Ensure that @tailwindcss/browser does not pollute the global namespace (#15978)
• Ensure that tailwind-merge is not scanned when using the Vite plugin (#16005)
• Ensure CSS theme variables are available within shadow roots (#15975)
• Fix crash when project lives in the / directory (#15988)
• Ensure custom variants have a non-empty selector list (#16009)
• Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#15927)
• Upgrade: Migrate leading-[1] to leading-none (#16004)
• Upgrade: Do not migrate arbitrary leading utilities to bare values (#16004)

v4.0.0

Holy shit it's actually done — we just tagged Tailwind CSS v4.0.

Tailwind CSS v4.0 is an all-new version of the framework optimized for performance and flexibility, with a reimagined configuration and customization experience, and taking full advantage of the latest advancements the web platform has to offer.

• New high-performance engine — where full builds are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
• Designed for the modern web — built on cutting-edge CSS features like cascade layers, registered custom properties with @property, and color-mix().
• Simplified installation — fewer dependencies, zero configuration, and just a single line of code in your CSS file.
• First-party Vite plugin — tight integration for maximum performance and minimum configuration.
• Automatic content detection — all of your template files are discovered automatically, with no configuration required.
• Built-in import support — no additional tooling necessary to bundle multiple CSS files.
• CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
• CSS theme variables — all of your design tokens exposed as native CSS variables so you can access them anywhere.
• Dynamic utility values and variants — stop guessing what values exist in your spacing scale, or extending your configuration for things like basic data attributes.
• Modernized P3 color palette — a redesigned, more vivid color palette that takes full advantage of modern display technology.
• Container queries — first-class APIs for styling elements based on their container size, no plugins required.
• New 3D transform utilities — transform elements in 3D space directly in your HTML.
• Expanded gradient APIs — radial and conic gradients, interpolation modes, and more.
• @​starting-style support — a new variant you can use to create enter and exit transitions, without the need for JavaScript.
• not-* variant — style an element only when it doesn't match another variant, custom selector, or media or feature query.

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.0.1] - 2025-01-29

Added

• Include :open pseudo-class in existing open variant (#15349)

Fixed

• Remove invalid min-w/h-none utilities (#15845)
• Discard CSS variable shorthand utilities that don't use valid CSS variables (#15738)
• Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#15921)
• Ensure font-size utilities with unknown modifier don't generate CSS (#15921)
• Don’t suggest font weight utilities more than once (#15857)
• Suggest container query variants (#15857)
• Disable bare value suggestions when not using the --spacing variable (#15857)
• Ensure suggested classes are properly sorted (#15857)
• Don’t look at .gitignore files outside initialized repos (#15941)
• Find utilities when using the Svelte class shorthand syntax across multiple lines (#15974)
• Find utilities when using the Angular class shorthand syntax (#15974)
• Find utilities when using functions inside arrays (#15974)
• Ensure that @tailwindcss/browser does not pollute the global namespace (#15978)
• Ensure that tailwind-merge is not scanned when using the Vite plugin (#16005)
• Ensure CSS theme variables are available within shadow roots (#15975)
• Fix crash when project lives in the / directory (#15988)
• Ensure custom variants have a non-empty selector list (#16009)
• Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#15927)
• Upgrade: Migrate leading-[1] to leading-none (#16004)
• Upgrade: Do not migrate arbitrary leading utilities to bare values (#16004)

[4.0.0] - 2025-01-21

Added

• New high-performance engine — where full builds are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
• Designed for the modern web — built on cutting-edge CSS features like cascade layers, registered custom properties with @property, and color-mix().
• Simplified installation — fewer dependencies, zero configuration, and just a single line of code in your CSS file.
• First-party Vite plugin — tight integration for maximum performance and minimum configuration.
• Automatic content detection — all of your template files are discovered automatically, with no configuration required.
• Built-in import support — no additional tooling necessary to bundle multiple CSS files.
• CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
• CSS theme variables — all of your design tokens exposed as native CSS variables so you can access them anywhere.
• Dynamic utility values and variants — stop guessing what values exist in your spacing scale, or extending your configuration for things like basic data attributes.
• Modernized P3 color palette — a redesigned, more vivid color palette that takes full advantage of modern display technology.
• Container queries — first-class APIs for styling elements based on their container size, no plugins required.
• New 3D transform utilities — transform elements in 3D space directly in your HTML.
• Expanded gradient APIs — radial and conic gradients, interpolation modes, and more.
• @​starting-style support — a new variant you can use to create enter and exit transitions, without the need for JavaScript.
• not-* variant — style an element only when it doesn't match another variant, custom selector, or media or feature query.
• Even more new utilities and variants — including support for color-scheme, field-sizing, complex shadows, inert, and more.

... (truncated)

Commits

• 0655209 Prepare v4.0.1 release (#16018)
• 9fef2bd Add :host rule to @theme layer (#15975)
• 924dd69 Ensure @custom-variant foo () has a non-empty selector list (#16009)
• 965048c Remove the force variant (#16007)
• 1eb2980 Fix IntelliSense class suggestions (#15857)
• f1221b3 Ensure font-size utilities with none modifier works e.g.: text-sm/none (#...
• 6dd4c33 Include :open in the open variant (#15349)
• 193fc60 Ensure CSS variable shorthand uses valid CSS variables (#15738)
• 7e20c3b Remove min-w/h-none (#15845)
• a8c54ac Prepare v4.0.0 release (#15693)
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions