build(deps): bump the docs-dependencies group in /docs with 5 updates

[dependabot]

Bumps the docs-dependencies group in /docs with 5 updates:

Package	From	To
@astrojs/starlight	0.31.1	0.32.0
@tailwindcss/vite	4.0.5	4.0.6
astro	5.2.5	5.3.0
tailwindcss	4.0.5	4.0.6
prettier	3.5.0	3.5.1

Updates @astrojs/starlight from 0.31.1 to 0.32.0

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.32.0

Minor Changes

• #2390 f493361 Thanks @​delucis! - Moves route data to Astro.locals instead of passing it down via component props

  ⚠️ Breaking change: Previously, all of Starlight’s templating components, including user or plugin overrides, had access to a data object for the current route via Astro.props. This data is now available as Astro.locals.starlightRoute instead.

  To update, refactor any component overrides you have:

  • Remove imports of @astrojs/starlight/props, which is now deprecated.
  • Update code that accesses Astro.props to use Astro.locals.starlightRoute instead.
  • Remove any spreading of {...Astro.props} into child components, which is no longer required.

  In the following example, a custom override for Starlight’s LastUpdated component is updated for the new style:

  ---
  import Default from '@astrojs/starlight/components/LastUpdated.astro';
  - import type { Props } from '@astrojs/starlight/props';
  
  const { lastUpdated } = Astro.props;
  
  
  const { lastUpdated } = Astro.locals.starlightRoute;
  
  const updatedThisYear = lastUpdated?.getFullYear() === new Date().getFullYear();
  {updatedThisYear && (
  
  <Default {...Astro.props}><slot /></Default>
  
  
  <Default><slot /></Default>
  )}

Community Starlight plugins may also need to be manually updated to work with Starlight 0.32. If you encounter any issues, please reach out to the plugin author to see if it is a known issue or if an updated version is being worked on.

#2578 f895f75 Thanks @​HiDeoo! - Deprecates the Starlight plugin setup hook in favor of the new config:setup hook which provides the same functionality.

⚠️ BREAKING CHANGE:

The Starlight plugin setup hook is now deprecated and will be removed in a future release. Please update your plugins to use the new config:setup hook instead.

export default {
  name: 'plugin-with-translations',
  hooks: {
-   'setup'({ config }) {
+   'config:setup'({ config }) {
      // Your plugin configuration setup code
    },

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.32.0

Minor Changes

• #2390 f493361 Thanks @​delucis! - Moves route data to Astro.locals instead of passing it down via component props

  ⚠️ Breaking change: Previously, all of Starlight’s templating components, including user or plugin overrides, had access to a data object for the current route via Astro.props. This data is now available as Astro.locals.starlightRoute instead.

  To update, refactor any component overrides you have:

  • Remove imports of @astrojs/starlight/props, which is now deprecated.
  • Update code that accesses Astro.props to use Astro.locals.starlightRoute instead.
  • Remove any spreading of {...Astro.props} into child components, which is no longer required.

  In the following example, a custom override for Starlight’s LastUpdated component is updated for the new style:

  ---
  import Default from '@astrojs/starlight/components/LastUpdated.astro';
  - import type { Props } from '@astrojs/starlight/props';
  
  const { lastUpdated } = Astro.props;
  
  
  const { lastUpdated } = Astro.locals.starlightRoute;
  
  const updatedThisYear = lastUpdated?.getFullYear() === new Date().getFullYear();
  {updatedThisYear && (
  
  <Default {...Astro.props}><slot /></Default>
  
  
  <Default><slot /></Default>
  )}

Community Starlight plugins may also need to be manually updated to work with Starlight 0.32. If you encounter any issues, please reach out to the plugin author to see if it is a known issue or if an updated version is being worked on.

#2578 f895f75 Thanks @​HiDeoo! - Deprecates the Starlight plugin setup hook in favor of the new config:setup hook which provides the same functionality.

⚠️ BREAKING CHANGE:

The Starlight plugin setup hook is now deprecated and will be removed in a future release. Please update your plugins to use the new config:setup hook instead.

export default {
  name: 'plugin-with-translations',
  hooks: {
-   'setup'({ config }) {
+   'config:setup'({ config }) {
      // Your plugin configuration setup code

... (truncated)

Commits

• 9b32c6a [ci] release (#2861)
• f493361 Move route data to Astro.locals (#2390)
• f895f75 Expose FS translation system to plugins (#2578)
• 2df9d05 Support multisite search on pagefind (#2858)
• 9b32ba9 Fix some Pagefind UI issues (#2848)
• d828556 Update Vitest to latest (#2857)
• See full diff in compare view

Updates @tailwindcss/vite from 4.0.5 to 4.0.6

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.0.6

Fixed

• Revert change to no longer include theme variables that aren't used in compiled CSS (#16403)

Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.0.6] - 2025-02-10

Fixed

• Revert change to no longer include theme variables that aren't used in compiled CSS (#16403)

Fixed

• Upgrade: Don't migrate blur to blur-sm when used with Next.js <Image placeholder="blur" /> (#16405)

Commits

• d045aaa Prepare v4.0.6 (#16407)
• See full diff in compare view

Updates astro from 5.2.5 to 5.3.0

Release notes

Sourced from astro's releases.

[email protected]

Minor Changes

• #13210 344e9bc Thanks @​VitaliyR! - Handle HEAD requests to an endpoint when a handler is not defined.

  If an endpoint defines a handler for GET, but does not define a handler for HEAD, Astro will call the GET handler and return the headers and status but an empty body.

• #13195 3b66955 Thanks @​MatthewLymer! - Improves SSR performance for synchronous components by avoiding the use of Promises. With this change, SSR rendering of on-demand pages can be up to 4x faster.

• #13145 8d4e566 Thanks @​ascorbic! - Adds support for adapters auto-configuring experimental session storage drivers.

  Adapters can now configure a default session storage driver when the experimental.session flag is enabled. If a hosting platform has a storage primitive that can be used for session storage, the adapter can automatically configure the session storage using that driver. This allows Astro to provide a more seamless experience for users who want to use sessions without needing to manually configure the session storage.

Patch Changes

• #13145 8d4e566 Thanks @​ascorbic! - ⚠️ BREAKING CHANGE FOR EXPERIMENTAL SESSIONS ONLY ⚠️

  Changes the experimental.session option to a boolean flag and moves session config to a top-level value. This change is to allow the new automatic session driver support. You now need to separately enable the experimental.session flag, and then configure the session driver using the top-level session key if providing manual configuration.

  defineConfig({
    // ...
    experimental: {
  -    session: {
  -      driver: 'upstash',
  -    },
  +    session: true,
    },
  +  session: {
  +    driver: 'upstash',
  +  },
  });

  You no longer need to configure a session driver if you are using an adapter that supports automatic session driver configuration and wish to use its default settings.

  defineConfig({
    adapter: node({
      mode: "standalone",
    }),
    experimental: {
  -    session: {
  -      driver: 'fs',
  -      cookie: 'astro-cookie',
  -    },
  +    session: true,
    },
  +  session: {
  +    cookie: 'astro-cookie',

... (truncated)

Changelog

Sourced from astro's changelog.

5.3.0

Minor Changes

• #13210 344e9bc Thanks @​VitaliyR! - Handle HEAD requests to an endpoint when a handler is not defined.

  If an endpoint defines a handler for GET, but does not define a handler for HEAD, Astro will call the GET handler and return the headers and status but an empty body.

• #13195 3b66955 Thanks @​MatthewLymer! - Improves SSR performance for synchronous components by avoiding the use of Promises. With this change, SSR rendering of on-demand pages can be up to 4x faster.

• #13145 8d4e566 Thanks @​ascorbic! - Adds support for adapters auto-configuring experimental session storage drivers.

  Adapters can now configure a default session storage driver when the experimental.session flag is enabled. If a hosting platform has a storage primitive that can be used for session storage, the adapter can automatically configure the session storage using that driver. This allows Astro to provide a more seamless experience for users who want to use sessions without needing to manually configure the session storage.

Patch Changes

• #13145 8d4e566 Thanks @​ascorbic! - ⚠️ BREAKING CHANGE FOR EXPERIMENTAL SESSIONS ONLY ⚠️

  Changes the experimental.session option to a boolean flag and moves session config to a top-level value. This change is to allow the new automatic session driver support. You now need to separately enable the experimental.session flag, and then configure the session driver using the top-level session key if providing manual configuration.

  defineConfig({
    // ...
    experimental: {
  -    session: {
  -      driver: 'upstash',
  -    },
  +    session: true,
    },
  +  session: {
  +    driver: 'upstash',
  +  },
  });

  You no longer need to configure a session driver if you are using an adapter that supports automatic session driver configuration and wish to use its default settings.

  defineConfig({
    adapter: node({
      mode: "standalone",
    }),
    experimental: {
  -    session: {
  -      driver: 'fs',
  -      cookie: 'astro-cookie',
  -    },
  +    session: true,
    },
  +  session: {

... (truncated)

Commits

• adb58f9 [ci] release (#13230)
• 5c6d58a test: update test assertion after test rename (#13242)
• 54d36c9 docs: remove kind heading (#13243)
• 723c843 chore: move session to top-level config option (#13241)
• d79ee8c [ci] format
• ee6d2cc chore: reword error message (#13240)
• 94b91a4 [ci] format
• 2ed67d5 fix: respond with 200 to HEAD requests for non-prerendered pages as well (#13...
• f392bef [ci] format
• 344e9bc fix: default head requests for endpoints when no explicit head method… (#13210)
• Additional commits viewable in compare view

Updates tailwindcss from 4.0.5 to 4.0.6

Release notes

Sourced from tailwindcss's releases.

v4.0.6

Fixed

• Revert change to no longer include theme variables that aren't used in compiled CSS (#16403)

Changelog

Sourced from tailwindcss's changelog.

[4.0.6] - 2025-02-10

Fixed

• Revert change to no longer include theme variables that aren't used in compiled CSS (#16403)

Fixed

• Upgrade: Don't migrate blur to blur-sm when used with Next.js <Image placeholder="blur" /> (#16405)

Commits

• d045aaa Prepare v4.0.6 (#16407)
• 9bbe2e3 Revert: Only expose used CSS variables (#16403)
• aaf66b0 Fix mismatched comment numbers in styles (#16380)
• a659159 Bump and pin prettier (#16382)
• See full diff in compare view

Updates prettier from 3.5.0 to 3.5.1

Release notes

Sourced from prettier's releases.

3.5.1

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.5.1

diff

Fix CLI crash when cache for old version exists (#17100 by @​sosukesuzuki)

Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.

Support dockercompose and github-actions-workflow in VSCode (#17101 by @​remcohaszing)

Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.

Commits

• 34f02bd Release 3.5.1
• 61c0129 Invalidate outdated cache file (#17100)
• 9cf8ec2 Support dockercompose and github-actions-workflow (#17101)
• 59e3696 Remove blog-post-intro (#17102)
• 92ac6d0 Add missing option experimentalOperatorPosition types (#17091)
• 8b1dda2 docs: avoid using .html extension for blog posts (#17090)
• f95cfbc Playground: Enable v3.5.0 features (#17093)
• df43d96 Fix blog title
• a4940b3 Release blog for 3.5 (#17020)
• 8810b5b run prettier
• 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

[github-actions]

PR Preview Action v1.6.0
Preview removed because the pull request was closed.
2025-02-17 08:37 UTC