Skip to content

Bump astro from 4.12.2 to 6.1.6 #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

Bump astro from 4.12.2 to 6.1.6 #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/astro/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"@astrojs/check": "^0.5.10",
"@astrojs/node": "^8.2.5",
"@sentry/astro": "8.9.2",
"astro": "^4.7.0",
"astro": "^6.1.6",
Copy link
Copy Markdown

@cursor cursor Bot Apr 21, 2026

Choose a reason for hiding this comment

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

Astro 6 removed output: 'hybrid' causing build failure

High Severity

Bumping astro to ^6.1.6 breaks the project because output: 'hybrid' was removed in Astro 5.0. The astro.config.mjs still uses output: 'hybrid', which will now throw an error at startup. In Astro 5+, the hybrid behavior was merged into output: 'static', so the config needs to be updated (or the output key removed entirely).

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 07e2b55. Configure here.

Copy link
Copy Markdown

@cursor cursor Bot Apr 21, 2026

Choose a reason for hiding this comment

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

@astrojs/node v8 incompatible with Astro 6

High Severity

The @astrojs/node dependency at ^8.2.5 is incompatible with Astro 6. The @astrojs/node v8.x series targets Astro 4.x, v9.x targets Astro 5.x, and v10.x targets Astro 6.x. This will cause peer dependency conflicts and likely runtime failures since the adapter's internal APIs changed across these major versions.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 07e2b55. Configure here.

Copy link
Copy Markdown

@cursor cursor Bot Apr 21, 2026

Choose a reason for hiding this comment

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

@sentry/astro 8.9.2 incompatible with Astro 6 internals

High Severity

The pinned @sentry/astro at 8.9.2 predates Astro 6 support, which was only added in a later version (PR #19745, March 2026). Astro 6 changed internal middleware context APIs — specifically, the route manifest moved from ctx.[Symbol.for('context.routes')] to ctx.[Symbol.for('astro.pipeline')]. Version 8.9.2 will fail at runtime when its middleware tries to access the old symbols.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 07e2b55. Configure here.

"typescript": "^5.4.5"
}
}
Loading
Loading