Skip to content

docs(deps)(deps): bump astro and @astrojs/starlight in /docs#1346

Merged
rumblefrog merged 3 commits into
mainfrom
dependabot/npm_and_yarn/docs/multi-a56432c679
May 11, 2026
Merged

docs(deps)(deps): bump astro and @astrojs/starlight in /docs#1346
rumblefrog merged 3 commits into
mainfrom
dependabot/npm_and_yarn/docs/multi-a56432c679

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 11, 2026

Copy link
Copy Markdown
Contributor

Bumps astro and @astrojs/starlight. These dependencies needed to be updated together.
Updates astro from 5.18.1 to 6.3.1

Release notes

Sourced from astro's releases.

astro@6.3.1

Patch Changes

  • #16646 15fbc41 Thanks @​matthewp! - Fixes local images returning 404 on non-prerendered pages when using the generic image endpoint

astro@6.3.0

Minor Changes

  • #16366 d69f858 Thanks @​matthewp! - Adds a new experimental.advancedRouting option that lets you take full control of Astro's request handling pipeline by creating a src/app.ts file in your project.

    Today, Astro handles every incoming request through a fixed internal pipeline: trailing slash normalization, redirects, actions, middleware, page rendering, i18n, and so on. That pipeline works great for most sites, but as projects grow you often want to run your own logic between those steps — an auth check before rendering, a rate limiter before actions, custom logging around the whole stack. Advanced routing gives you that control.

    When enabled, Astro looks for a src/app.ts file in your project. If it finds one, that file becomes the entrypoint for all server-rendered requests. You compose the pipeline yourself using the handlers Astro provides, and you can slot your own logic anywhere in the chain.

    Enabling advanced routing

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    export default defineConfig({
    experimental: {
    advancedRouting: true,
    },
    });

    Two ways to build your pipeline

    Astro ships two entrypoints for advanced routing: astro/fetch and astro/hono.

    astro/fetch is a low-level, framework-free API built on the Web Fetch standard. You create a FetchState from the incoming request, then call handler functions in sequence. Each handler takes the state, does its work, and returns a Response (or undefined to pass through). This is the core primitive that everything else is built on:

    // src/app.ts
    import {
      FetchState,
      trailingSlash,
      redirects,
      actions,
      middleware,
      pages,
      i18n,
    } from 'astro/fetch';
    export default {
    async fetch(request: Request) {
    const state = new FetchState(request);
    // Early exits — these return a Response only when they apply.

... (truncated)

Changelog

Sourced from astro's changelog.

6.3.1

Patch Changes

  • #16646 15fbc41 Thanks @​matthewp! - Fixes local images returning 404 on non-prerendered pages when using the generic image endpoint

6.3.0

Minor Changes

  • #16366 d69f858 Thanks @​matthewp! - Adds a new experimental.advancedRouting option that lets you take full control of Astro's request handling pipeline by creating a src/app.ts file in your project.

    Today, Astro handles every incoming request through a fixed internal pipeline: trailing slash normalization, redirects, actions, middleware, page rendering, i18n, and so on. That pipeline works great for most sites, but as projects grow you often want to run your own logic between those steps — an auth check before rendering, a rate limiter before actions, custom logging around the whole stack. Advanced routing gives you that control.

    When enabled, Astro looks for a src/app.ts file in your project. If it finds one, that file becomes the entrypoint for all server-rendered requests. You compose the pipeline yourself using the handlers Astro provides, and you can slot your own logic anywhere in the chain.

    Enabling advanced routing

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    export default defineConfig({
    experimental: {
    advancedRouting: true,
    },
    });

    Two ways to build your pipeline

    Astro ships two entrypoints for advanced routing: astro/fetch and astro/hono.

    astro/fetch is a low-level, framework-free API built on the Web Fetch standard. You create a FetchState from the incoming request, then call handler functions in sequence. Each handler takes the state, does its work, and returns a Response (or undefined to pass through). This is the core primitive that everything else is built on:

    // src/app.ts
    import {
      FetchState,
      trailingSlash,
      redirects,
      actions,
      middleware,
      pages,
      i18n,
    } from 'astro/fetch';
    export default {
    async fetch(request: Request) {
    const state = new FetchState(request);

... (truncated)

Commits

Updates @astrojs/starlight from 0.30.6 to 0.39.2

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.39.2

Patch Changes

@​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

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
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​astrojs/starlight since your current version.


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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot @github

dependabot Bot commented on behalf of github May 11, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: docs. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label May 11, 2026
@rumblefrog rumblefrog force-pushed the dependabot/npm_and_yarn/docs/multi-a56432c679 branch from d29af24 to 83d27d1 Compare May 11, 2026 05:38
dependabot Bot and others added 3 commits May 11, 2026 01:40
Bumps [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) and [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight). These dependencies needed to be updated together.

Updates `astro` from 5.18.1 to 6.3.1
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/astro@6.3.1/packages/astro)

Updates `@astrojs/starlight` from 0.30.6 to 0.39.2
- [Release notes](https://github.com/withastro/starlight/releases)
- [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md)
- [Commits](https://github.com/withastro/starlight/commits/@astrojs/starlight@0.39.2/packages/starlight)

---
updated-dependencies:
- dependency-name: astro
  dependency-version: 6.3.1
  dependency-type: direct:production
- dependency-name: "@astrojs/starlight"
  dependency-version: 0.39.2
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Astro 6 raised its Node floor to `>=22.12` (`engines.node` in the
astro@6.x manifest, EBADENGINE warning at install time + a hard
"Node.js v20 is not supported by Astro!" abort at `astro build`).
Bumping the docs-build / docs-screenshots-build / docs-screenshots-capture
runners to Node 22 unblocks the paired astro@^5 → ^6 + @astrojs/starlight@^0.30
→ ^0.39 dependency bump in this PR.

The web panel's runtime stack is unaffected (PHP 8.5; the only
client-side TS check runs over `web/scripts/` and stays on Node 20
via `ts-check.yml`).
Starlight 0.33 (in the 0.30 → 0.39 bump landing here) changed the
`social` integration option from a `Record<KnownPlatform, url>` map
to a `[{icon, label, href}]` array. The old shape now fails the
config schema with "Starlight v0.33.0 changed the `social` configuration
syntax. Please specify an array of link items instead of an object."

Migrating both the GitHub and Discord entries preserves the topbar
icon row exactly. The pre-fix comment block at the call site already
anticipated this exact migration; the surrounding rationale was
moved into the new comment.
@rumblefrog rumblefrog force-pushed the dependabot/npm_and_yarn/docs/multi-a56432c679 branch from 83d27d1 to 765ce0e Compare May 11, 2026 05:40
@rumblefrog rumblefrog added this pull request to the merge queue May 11, 2026
Merged via the queue into main with commit 27edfe3 May 11, 2026
4 checks passed
@rumblefrog rumblefrog deleted the dependabot/npm_and_yarn/docs/multi-a56432c679 branch May 11, 2026 05:41
Rushaway pushed a commit to srcdslab/sourcebans-pp that referenced this pull request May 15, 2026
…in `if:` (sbpp#1350)

sbpp#1347's skip-when-unconfigured guard used `if: secrets.DOCS_DEPLOY_PAT != ''`
on the dispatch step. `secrets.*` isn't available in `if:` at any scope
(workflow / job / step) per the Actions context-availability table — the
parser rejects the file with "Unrecognized named-value: 'secrets'" before
any job runs, so every push records a red workflow-file-issue run with no
jobs (visible on the sbpp#1346 dependabot push, run 25652463088). Exactly the
failure mode the guard was meant to prevent.

Fix: read the secret into a precheck step's `env:` (where `secrets.*` IS
allowed), shell-test for presence, emit a `configured=true|false` step
output, gate the dispatch step on `steps.pat.outputs.configured == 'true'`
(`steps.*` IS available in step `if:`). Operator-facing UX unchanged —
dispatch step still shows as Skipped until the PAT is set, run is green.

Both the file-level comment block and the inline step comment now spell
out the actual context-availability rule so a future reader doesn't reach
for the same broken shape.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant