chore(deps): bump @astrojs/starlight from 0.38.4 to 0.39.2 in /docs

[dependabot]

Bumps @astrojs/starlight from 0.38.4 to 0.39.2.

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.39.2

Patch Changes

• #3890 2d05e18 Thanks @​tats-u! - Fixes CSS selector for text-autospace styles in Chromium browsers

@​astrojs/starlight@​0.39.1

Patch Changes

• #3885 010eed1 Thanks @​ArmandPhilippot! - Fixes the version mentioned in an error message related to autogenerated sidebar groups support.

• #3887 b3c6990 Thanks @​delucis! - Adds 13 new icons: clock, desktop, mobile-android, window, database, server, code-branch, notes, question, question-circle, analytics, padlock, and solidjs.

@​astrojs/starlight@​0.39.0

Minor Changes

• #3618 dcf6d09 Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: This release changes how autogenerated links work in Starlight’s sidebar configuration.

  If you have sidebar groups using the autogenerate key, you must now wrap that configuration in an items array:

  {
      label: 'My group',
  -   autogenerate: { directory: 'some-dir' },
  +   items: [{ autogenerate: { directory: 'some-dir' } }],
  }

  This change unlocks the possibility to mix autogenerated links and other links in a single group, for example:

  {
    label: 'Mixed group',
    items: [
      'example-page',
      { autogenerate: { directory: 'examples' } },
      { label: 'More examples', link: 'https://example.com' },
    ],
  }

  This release also updates the shape of autogenerated sidebar entries in route data. Autogenerated links and groups in Astro.locals.starlightRoute.sidebar now include an autogenerate object with the configured directory value:

  {
    type: 'link',
    label: 'Example',
    href: '/examples/example/',
    isCurrent: false,
    autogenerate: { directory: 'examples' }
  }

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.39.2

Patch Changes

• #3890 2d05e18 Thanks @​tats-u! - Fixes CSS selector for text-autospace styles in Chromium browsers

0.39.1

Patch Changes

• #3885 010eed1 Thanks @​ArmandPhilippot! - Fixes the version mentioned in an error message related to autogenerated sidebar groups support.

• #3887 b3c6990 Thanks @​delucis! - Adds 13 new icons: clock, desktop, mobile-android, window, database, server, code-branch, notes, question, question-circle, analytics, padlock, and solidjs.

0.39.0

Minor Changes

• #3618 dcf6d09 Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: This release changes how autogenerated links work in Starlight’s sidebar configuration.

  If you have sidebar groups using the autogenerate key, you must now wrap that configuration in an items array:

  {
      label: 'My group',
  -   autogenerate: { directory: 'some-dir' },
  +   items: [{ autogenerate: { directory: 'some-dir' } }],
  }

  This change unlocks the possibility to mix autogenerated links and other links in a single group, for example:

  {
    label: 'Mixed group',
    items: [
      'example-page',
      { autogenerate: { directory: 'examples' } },
      { label: 'More examples', link: 'https://example.com' },
    ],
  }

  This release also updates the shape of autogenerated sidebar entries in route data. Autogenerated links and groups in Astro.locals.starlightRoute.sidebar now include an autogenerate object with the configured directory value:

  {
    type: 'link',
    label: 'Example',
    href: '/examples/example/',

... (truncated)

Commits

• 76ff51e [ci] release (#3891)
• 2d05e18 Make sure to enable text-autospace even in non-Firefox browsers (#3890)
• 0c0acc0 [ci] release (#3886)
• b3c6990 Add new icons to Starlight’s built-in set (#3887)
• 010eed1 fix: update the version mentioned in autogenerate error message (#3885)
• c89c144 [ci] release (#3883)
• dcf6d09 Refactor autogenerated sidebar groups (#3618)
• 6672c35 Update i18next (#3858)
• 6b18976 [ci] format
• 417a66c Enable text-autospace in Chinese and Japanese documents (#3872)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

❌ Smoke Project encountered failures. Check the logs for details.

[github-actions]

❌ Smoke Multi PR failed to create multiple PRs. Check the logs.

[github-actions]

Hey @app/dependabot 👋 — thanks for the automated dependency update!

Unfortunately, this PR doesn't align with the contribution process for github/gh-aw. Here's why:

🚫 Process violation: The CONTRIBUTING.md clearly states:

Traditional Pull Requests Are Not Enabled for non-Core team members: If you are not part of the core team, please do not create pull requests directly. Instead, you create detailed agentic plans in issues, discuss with the team, and a core team member will create and implement the PR for you using agents.

Since Dependabot is not part of the core team and this PR was created directly without following the "agentic plan in an issue" process, it violates the contribution guidelines. The project uses agentic development where all PRs should come from the core team using Copilot coding agents or local agents, not automated bots.

📋 What should happen instead:

1. Dependency updates should be identified and proposed as issues with agentic plans
2. A core team member should review the plan
3. The core team member creates and implements the PR using their coding agent

This approach ensures all changes go through the project's agentic workflow, even routine dependency updates.

Disable Dependabot PRs for the github/gh-aw repository. Instead, configure Dependabot to only create issues (not PRs) so that dependency updates can be reviewed and implemented by core team members using coding agents, following the agentic development workflow described in CONTRIBUTING.md.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• patchdiff.githubusercontent.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "patchdiff.githubusercontent.com"

See Network Configuration for more information.

Generated by ✅ Contribution Check · ◷

[dependabot]

Looks like @astrojs/starlight is up-to-date now, so this is no longer needed.