Skip to content

build(deps): bump astro from 5.18.1 to 6.1.8 in /docs in the npm_and_yarn group across 1 directory#812

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/docs/npm_and_yarn-0f5eb44cbf
Closed

build(deps): bump astro from 5.18.1 to 6.1.8 in /docs in the npm_and_yarn group across 1 directory#812
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/docs/npm_and_yarn-0f5eb44cbf

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Apr 22, 2026

Bumps the npm_and_yarn group with 1 update in the /docs directory: astro.

Updates astro from 5.18.1 to 6.1.8

Release notes

Sourced from astro's releases.

astro@6.1.8

Patch Changes

  • #16367 a6866a7 Thanks @​ematipico! - Fixes an issue where build output files could contain special characters (!, ~, {, }) in their names, causing deploy failures on platforms like Netlify.

  • #16381 217c5b3 Thanks @​ematipico! - Slightly improved the performance of the dev server by caching the internal crawling of the dependencies of a project.

  • #16348 7d26cd7 Thanks @​ocavue! - Fixes a bug where emitted assets during a client build would contain always fresh, new hashes in their name. Now the build should be more stable.

  • #16317 d012bfe Thanks @​das-peter! - Fixes a bug where allowedDomains weren't correctly propagated when using the development server.

  • #16379 5a84551 Thanks @​martrapp! - Improves Vue scoped style handling in DEV mode during client router navigation.

  • #16317 d012bfe Thanks @​das-peter! - Adds tests to verify settings are properly propagated when using the development server.

  • #16282 5b0fdaa Thanks @​jmurty! - Fixes build errors on platforms with skew protection enabled (e.g. Vercel, Netlify) for inter-chunk Javascript using dynamic imports

  • Updated dependencies [e0b240e]:

    • @​astrojs/telemetry@​3.3.1

astro@6.1.7

Patch Changes

  • #16027 c62516b Thanks @​fkatsuhiro! - Fixes a bug where remote image dimensions were not validated during static builds on Netlify.

  • #16311 94048f2 Thanks @​Arecsu! - Fixes --port flag being ignored after a Vite-triggered server restart (e.g. when a .env file changes)

  • #16316 0fcd04c Thanks @​ematipico! - Fixes the /_image endpoint accepting an arbitrary f=svg query parameter and serving non-SVG content as image/svg+xml. The endpoint now validates that the source is actually SVG before honoring f=svg, matching the same guard already enforced on the <Image> component path.

astro@6.1.6

Patch Changes

  • #16202 b5c2fba Thanks @​matthewp! - Fixes Actions failing with ActionsWithoutServerOutputError when using output: 'static' with an adapter

  • #16303 b06eabf Thanks @​matthewp! - Improves handling of special characters in inline <script> content

  • #14924 bb4586a Thanks @​aralroca! - Fixes SCSS and CSS module file changes triggering a full page reload instead of hot-updating styles in place during development

astro@6.1.5

Patch Changes

  • #16171 5bcd03c Thanks @​Desel72! - Fixes a build error that occurred when a pre-rendered page used the <Picture> component and another page called render() on content collection entries.

  • #16239 7c65c04 Thanks @​dataCenter430! - Fixes sync content inside <Fragment> not streaming to the browser until all async sibling expressions have resolved.

  • #16242 686c312 Thanks @​martrapp! - Revives UnoCSS in dev mode when used with the client router.

    This change partly reverts #16089, which in hindsight turned out to be too general. Instead of automatically persisting all style sheets, we now do this only for styles from Vue components.

  • #16192 79d86b8 Thanks @​alexanderniebuhr! - Uses today’s date for Cloudflare compatibility_date in astro add cloudflare

... (truncated)

Changelog

Sourced from astro's changelog.

6.1.8

Patch Changes

  • #16367 a6866a7 Thanks @​ematipico! - Fixes an issue where build output files could contain special characters (!, ~, {, }) in their names, causing deploy failures on platforms like Netlify.

  • #16381 217c5b3 Thanks @​ematipico! - Slightly improved the performance of the dev server by caching the internal crawling of the dependencies of a project.

  • #16348 7d26cd7 Thanks @​ocavue! - Fixes a bug where emitted assets during a client build would contain always fresh, new hashes in their name. Now the build should be more stable.

  • #16317 d012bfe Thanks @​das-peter! - Fixes a bug where allowedDomains weren't correctly propagated when using the development server.

  • #16379 5a84551 Thanks @​martrapp! - Improves Vue scoped style handling in DEV mode during client router navigation.

  • #16317 d012bfe Thanks @​das-peter! - Adds tests to verify settings are properly propagated when using the development server.

  • #16282 5b0fdaa Thanks @​jmurty! - Fixes build errors on platforms with skew protection enabled (e.g. Vercel, Netlify) for inter-chunk Javascript using dynamic imports

  • Updated dependencies [e0b240e]:

    • @​astrojs/telemetry@​3.3.1

6.1.7

Patch Changes

  • #16027 c62516b Thanks @​fkatsuhiro! - Fixes a bug where remote image dimensions were not validated during static builds on Netlify.

  • #16311 94048f2 Thanks @​Arecsu! - Fixes --port flag being ignored after a Vite-triggered server restart (e.g. when a .env file changes)

  • #16316 0fcd04c Thanks @​ematipico! - Fixes the /_image endpoint accepting an arbitrary f=svg query parameter and serving non-SVG content as image/svg+xml. The endpoint now validates that the source is actually SVG before honoring f=svg, matching the same guard already enforced on the <Image> component path.

6.1.6

Patch Changes

  • #16202 b5c2fba Thanks @​matthewp! - Fixes Actions failing with ActionsWithoutServerOutputError when using output: 'static' with an adapter

  • #16303 b06eabf Thanks @​matthewp! - Improves handling of special characters in inline <script> content

  • #14924 bb4586a Thanks @​aralroca! - Fixes SCSS and CSS module file changes triggering a full page reload instead of hot-updating styles in place during development

6.1.5

Patch Changes

  • #16171 5bcd03c Thanks @​Desel72! - Fixes a build error that occurred when a pre-rendered page used the <Picture> component and another page called render() on content collection entries.

  • #16239 7c65c04 Thanks @​dataCenter430! - Fixes sync content inside <Fragment> not streaming to the browser until all async sibling expressions have resolved.

  • #16242 686c312 Thanks @​martrapp! - Revives UnoCSS in dev mode when used with the client router.

... (truncated)

Commits

Dependabot compatibility score

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

Bumps the npm_and_yarn group with 1 update in the /docs directory: [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro).


Updates `astro` from 5.18.1 to 6.1.8
- [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.1.8/packages/astro)

---
updated-dependencies:
- dependency-name: astro
  dependency-version: 6.1.8
  dependency-type: direct:production
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 22, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Codecov Results 📊

138 passed | Total: 138 | Pass Rate: 100% | Execution Time: 0ms

📊 Comparison with Base Branch

Metric Change
Total Tests
Passed Tests
Failed Tests
Skipped Tests

✨ No test changes detected

All tests are passing successfully.

✅ Patch coverage is 100.00%. Project has 1950 uncovered lines.
❌ Project coverage is 95.19%. Comparing base (base) to head (head).

Coverage diff
@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
- Coverage    95.20%    95.19%    -0.01%
==========================================
  Files          282       282         —
  Lines        40577     40577         —
  Branches         0         0         —
==========================================
+ Hits         38633     38627        -6
- Misses        1944      1950        +6
- Partials         0         0         —

Generated by Codecov Action

Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 84f272f. Configure here.

Comment thread docs/package.json
"@astrojs/starlight": "^0.31.1",
"@sentry/astro": "^10.38.0",
"astro": "^5.1.1",
"astro": "^6.1.8",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starlight 0.31 incompatible with Astro 6 major upgrade

High Severity

Bumping astro to ^6.1.8 without upgrading @astrojs/starlight from ^0.31.1 breaks compatibility. Starlight 0.31 only supports Astro 5.x; Astro 6 support was introduced in Starlight 0.38.0. This will cause the docs build to fail because the Starlight integration cannot work with the new major version of Astro.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 84f272f. Configure here.

Comment thread docs/package.json
"@astrojs/starlight": "^0.31.1",
"@sentry/astro": "^10.38.0",
"astro": "^5.1.1",
"astro": "^6.1.8",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lockfile not updated, still resolves Astro 5.x

Medium Severity

The bun.lock file was not updated alongside the package.json change. The lockfile still records "astro": "^5.1.1" and resolves to astro@5.16.15, leaving the dependency tree completely out of sync with the new ^6.1.8 specifier. This happens because Dependabot is configured for npm_and_yarn but the project uses bun, so the lockfile is never regenerated. Running bun install will encounter a mismatch and attempt to re-resolve, but without updating the locked companion packages (@astrojs/mdx, astro-expressive-code, etc.) that also need Astro 6–compatible versions.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 84f272f. Configure here.

@BYK
Copy link
Copy Markdown
Member

BYK commented Apr 22, 2026

Superseded by #816, which does the full coordinated Astro 5 → 6 upgrade (bumps @astrojs/starlight 0.31 → 0.38 as well, migrates the legacy content-collections config to the Content Layer API, updates the deprecated social config shape, and ports the PageTitle/Header overrides to the new Astro.locals.starlightRoute route-data API). That PR regenerates bun.lock and has been verified locally with bun install --frozen-lockfile && bun run build.

@BYK BYK closed this Apr 22, 2026
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Apr 22, 2026

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/docs/npm_and_yarn-0f5eb44cbf branch April 22, 2026 12:31
BYK added a commit that referenced this pull request Apr 22, 2026
## Summary

- Supersedes #812 with the full coordinated Astro 5 → 6 upgrade for the
docs site.
- Bumps `astro` (`^5.1.1` → `^6.1.8`) and `@astrojs/starlight`
(`^0.31.1` → `^0.38.3`) together, regenerates `docs/bun.lock`.
- Applies the breaking-change migrations required by the new major
versions.

## Why #812 can't land on its own

Dependabot's PR only bumps `astro` in isolation. That breaks two ways:

1. **Immediate**: Dependabot regenerates `package-lock.json`, not
`bun.lock`, so `bun install --frozen-lockfile` fails in the `Build Docs`
CI job.
2. **Actual**: `@astrojs/starlight@0.31.1` pins `peerDependencies.astro`
to `^5.1.5`, and Astro 6 [removes the automatic legacy
content-collections backwards-compat
layer](https://docs.astro.build/en/guides/upgrade-to/v6/#legacy-content-collections-backwards-compatibility).
Starlight must move along with Astro.

## Changes

### Dependencies
- `astro`: `^5.1.1` → `^6.1.8`
- `@astrojs/starlight`: `^0.31.1` → `^0.38.3`
- `@sentry/astro`, `sharp`, `shiki` unchanged (already compatible)

### Content Layer API migration
Moved `docs/src/content/config.ts` → `docs/src/content.config.ts` and
rewrote it to pair `docsSchema()` with `docsLoader()`. Astro 6 removes
the automatic legacy content-collections backwards-compat layer, so
every collection must now go through the Content Layer API.

### Starlight config changes
- `social` config: deprecated object shorthand → array-of-entries form
(Starlight 0.33 breaking change).
- `PageTitle.astro` override: reads sidebar/entry from
`Astro.locals.starlightRoute` instead of `Astro.props` (the `Props` type
from `@astrojs/starlight/props` is deprecated and no longer populated by
Starlight).
- `Header.astro` override: same route-data migration; `slug` is now
`starlightRoute.id` (empty string on the landing page, per Starlight's
`normalizeIndexSlug`).

### Build scripts (Astro 6 Node engine)
Astro 6 enforces `engines.node >= 22.12.0` at runtime, but the
GitHub-hosted Ubuntu runner ships Node 20.20.2 and `astro`'s bin has
`#!/usr/bin/env node`. `docs/package.json` scripts (`dev`, `build`,
`preview`) now invoke astro via `bun --bun` so the build runs under Bun
and bypasses the Node shebang. Works transparently in CI and on local
machines stuck on Node 20.x.

## Out of scope
- No CLI code / repo-root lockfile changes — strictly `docs/`.
- No Tailwind migration (site has no Tailwind integration).

## Verification
```sh
cd docs
rm -rf node_modules
bun install --frozen-lockfile   # clean install, 538 packages
bun run build                   # 29 pages built, no errors
```

Closes #812
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant