Repository navigation
chore(docs): update Docusaurus to 3.10.2 and group docs security updates - #8
Merged
Merged
Conversation
- Both sites: @docusaurus/* 3.9.0 -> 3.10.2 plus npm audit fix,
78 -> 48 npm audit findings each. The rest come from Docusaurus's own
dependencies and need major bumps their parents don't allow yet.
- future.v4 is now an explicit flag object: 3.10 added
mdx1CompatDisabledByDefault (would break the generated {#id} headings)
and fasterByDefault (needs @docusaurus/faster) to `v4: true`. Both
stay off, so the build behaves as on 3.9.
- dependabot.yml: npm security updates for both sites in one grouped PR,
no routine version updates. Same change as srctool/camouflage#23.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Description
This is the same change as srctool/camouflage#23. The docs sites lock the same vulnerable npm packages as Camouflage's, but this repository's dependency graph is off, so GitHub raises no alerts for them.
npm audit fix.npm auditdrops from 78 to 48 findings per site.future.v4is now an explicit flag object. 3.10 added two flags tov4: true.mdx1CompatDisabledByDefaultbreaks the generated pages'{#id}headings.fasterByDefaultneeds the extra@docusaurus/fasterpackage. Both are off, so the build behaves as it did on 3.9.dependabot.yml: an npm entry for both sites that groups security updates into one PR and opens no routine version-update PRs.The remaining 48 findings are the same six build-time packages as in Camouflage (tinypool, serialize-javascript, uuid, katex, postcss-selector-parser, braces). Each needs a major bump their parents don't accept yet, so they wait for upstream Docusaurus releases.
After merging: turn on the dependency graph for this repository. Dependabot security updates are already on, and with this PR merged they arrive as one grouped PR instead of one per package.
Type of change
How Has This Been Tested?
npm run buildpasses fordocs/internalanddocs/usagewith no errors or warnings.docs/internal/build, e.g.id="kotlin-repository-and-modules").Breaking changes
None.
🤖 Generated with Claude Code