You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release includes major upgrades for the Astro framework and the Fastify static file server, introducing significant breaking changes that require developer action.
Top 3 Most Impactful Upgrades
astro 4.16.18 → 5.4.3 (High Risk): This major upgrade introduces several breaking changes. Key changes include the upgrade to Vite 6.0, a new Content Layer API that deprecates some legacy content collection behaviors, and the removal of hybrid rendering mode. The <ViewTransitions /> component has also been renamed, and CSRF protection is now enabled by default. Projects using MDX must upgrade the @astrojs/mdx integration. [1, 3, 6]
Recommendation: Review the official Astro v5 upgrade guide. Pay close attention to content collection definitions, MDX configuration, and rendering mode settings. Test thoroughly after upgrading dependencies.
@fastify/static 7.0.4 → 9.0.0 (High Risk): This upgrade spans two major versions. The most significant breaking change, introduced in v9.0.0, is to the setHeaders option. The function now receives a Fastify reply object instead of a Node.js res object. [4]
Recommendation: If you use the setHeaders function, you must refactor your code from res.setHeader('X-Test', 'Foo') to reply.header('X-Test', 'Foo') to avoid runtime errors. [4]
@astrojs/starlight 0.21.5 → 0.30.0 (Medium Risk): While a minor version upgrade, a potentially breaking change was introduced in v0.3.0 for autogenerated sidebars. Configuration now relies on the literal directory path instead of a slugified version. [11]
Recommendation: If you use autogenerated sidebars and have directories with spaces or special characters in their names, verify your sidebar configuration to ensure links are generated correctly. [11]
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
website/package.jsonwebsite/package-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-BRACEEXPANSION-18313044
SNYK-JS-JSYAML-18313070
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling