chore(deps): bump npm dependencies - #393
Merged
Merged
Conversation
Applies the Dependabot minor-and-patch group (#388) and the `@keystatic/astro` major (#361) on top of the advisory fixes from #389, as a single lockfile regeneration rather than three conflicting ones. Dependencies: - @astrojs/react 6.0.4 -> 6.0.5 - @astrojs/sitemap 3.7.3 -> 3.7.4 - @astrojs/vercel 11.0.7 -> 11.0.10 - @keystatic/astro 5.2.0 -> 6.0.0 - @keystatic/core 0.6.8 -> 0.6.9 - @types/react 19.2.18 -> 19.3.0 - @types/react-dom 19.2.4 -> 19.3.0 - astro-auto-import 0.5.2 -> 0.6.0 - astro-expressive-code 0.44.1 -> 0.44.2 - astro-seo 1.1.0 -> 1.2.0 - react, react-dom 19.2.8 -> 19.3.0 Dev dependencies: - eslint 10.9.0 -> 10.10.0 (dependency and the matching `overrides` pin) - globals 17.11.0 -> 17.12.0 - typescript-eslint 8.67.0 -> 8.70.0 `@astrojs/markdown-remark` is already at ^7.3.1 on main via #389, and astro stays at 7.3.3: this group does not touch it. The `@keystatic/astro` major is safe here. Its 6.0.0 peer range is `astro "5 || 6 || 7"`, so the major only drops astro 2/3/4 support and the repository already runs astro 7. Lockfile regenerated from the registry with npm 10 and no node_modules present, per CLAUDE.md. Verified: npm@10 ci --dry-run in sync, npm audit clean at both CI gates, lint clean (0 errors), build produces the same 291 pages and the same pagefind index (20 pages, 2987 words), and the home, blog, docs and provider-tab pages render with no console errors.
This was referenced Sep 17, 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.
Applies the Dependabot minor-and-patch group (#388) and the
@keystatic/astromajor (#361) on top of the advisory fixes from #389.Supersedes #388 and #361.
Why these are combined
Both Dependabot PRs edit
package.jsonandpackage-lock.json, and both predate the advisory fixes in #389, so each conflicts withmainand with the other. Landing them separately would mean three lockfile regenerations and three conflict resolutions to reach the same tree. This is one regeneration from the registry instead.Dependencies
@astrojs/react@astrojs/sitemap@astrojs/vercel@keystatic/astro@keystatic/core@types/react@types/react-domastro-auto-importastro-expressive-codeastro-seoreact,react-domDev dependencies:
eslint10.9.0 to 10.10.0 (both the dependency and the matchingoverridespin, as Dependabot proposed),globals17.11.0 to 17.12.0,typescript-eslint8.67.0 to 8.70.0.@astrojs/markdown-remarkis already at^7.3.1onmainvia #389, and astro stays at 7.3.3: this group does not touch either.On the
@keystatic/astromajorLow risk. The 6.0.0 peer range is
astro "5 || 6 || 7"against 5.2.0's"2 || 3 || 4 || 5 || 6 || 7", so the major only drops astro 2/3/4 support. This repository already runs astro 7.Verification
npx -y npm@10 ci --dry-runin syncnpm audit --audit-level=moderateandnpm audit --omit=dev --audit-level=highboth report 0 vulnerabilitiesnpm run lintclean, 0 errors (the same 15 pre-existing import-sort warnings; no source files are touched by this PR)npm run buildgreen, same 291 pages and same pagefind index (20 pages, 2987 words) asmain/blog,/docs/cli/installationand the provider-tab docs pages render with no console errorsLockfile regenerated from the registry with npm 10 and no
node_modulespresent, perCLAUDE.md.Note on
/keystaticWhile verifying this branch the Keystatic admin was blank in local dev. That turned out to be pre-existing on
mainand unrelated to these bumps: it reproduces with@keystatic/astro5.2.0 and is fixed separately in #392.