chore: basic dependency bump #485
Merged
Conversation
This file contains 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
✅ Deploy Preview for webmonetization-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There have been a few difficulties with this dependency bump.
Firstly, Starlight, as of now, has a compatibility issue with astro@5. This is being addressed (see withastro/starlight#2612)
Secondly, bumping up the @astrojs/starlight dependency caused compatibility issues with the
HeadHrefLangscomponent that is part of the astro-i18next module. Unfortunately, it seems this module is no longer being maintained. As such, I've removed it for now. HeadHrefLangs is a component from astro-i18next that generated tags with hreflang attributes for SEO, specifying alternate language versions of a webpage. This means we need to investigate a new way to build this in and probably use either a different community based plugin for this, or move over to Astro's Built-in i18n Support. This also has limitations which is why it needs more work to figure out the best path.