chore(deps): refresh all dependencies before v0.1.0 - #73
Merged
Conversation
Brings the lockfile to current within the declared ranges: astro 7.1.3 → 7.2.1, starlight 0.41.4 → 0.41.7, plus the transitive advisories the open dependabot PRs cover (nanoid 3.3.18, js-yaml 4.3.1, dompurify 3.4.13, fast-uri 3.1.5, postcss 8.5.26, svgo 4.0.2, @astrojs/rss 4.0.19, mermaid 11.16.1). Supersedes textrefs#33, textrefs#35, textrefs#37, textrefs#57, textrefs#64, textrefs#65, textrefs#66, textrefs#69, textrefs#70. TypeScript stays on 6.x: `astro check` refuses 7.0+ because the native compiler does not expose the programmatic API the language server needs (withastro/roadmap#1321).
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Aug 12, 2026
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
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.
Brings every npm dependency current ahead of the
v0.1.0tag, so the first citable baseline ships on maintained versions rather than carrying ten open dependabot PRs past the release.npm
npm updatewithin the declared ranges — nopackage.jsonrange edits were needed:Supersedes #33, #35, #37, #57, #64, #65, #66, #69, #70 — all of which target
main, which only moves at release time.TypeScript stays on 6.x
typescript@7.0.2is available butastro checkrefuses it: the native compiler does not yet expose the programmatic API@astrojs/language-serverrelies on (withastro/roadmap#1321). Verified locally — the check fails outright, so 7.x is not a near-term option regardless of the release.Still outstanding
actions/setup-nodev6 → v7 (#32) is committed locally but could not be pushed: the OAuth credential in use lacks theworkflowscope. Every other action is already pinned at its latest major (checkout v7, configure-pages v6, upload-pages-artifact v5, deploy-pages v5, action-gh-release v3, lychee-action v2, create-issue-from-file v6).Not taken here
Astro 7.2's
experimental.incrementalBuildis a real opportunity for this repo — the full build is ~8 min across 204k pages — but it requirescacheKeyreturn values from everygetStaticPaths(). That is its own change, not release plumbing.Verification
npm run verify:fastpasses locally (format, astro check, 21 tests, fixture build with link validation). Fullnpm run verifyagainst the real 67,959-reference registry runs in CI here.Part of #68.