chore(deps): bump @docusaurus/core from 3.9.2 to 3.10.0 in /docs#333
chore(deps): bump @docusaurus/core from 3.9.2 to 3.10.0 in /docs#333dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [@docusaurus/core](https://github.com/facebook/docusaurus/tree/HEAD/packages/docusaurus) from 3.9.2 to 3.10.0. - [Release notes](https://github.com/facebook/docusaurus/releases) - [Changelog](https://github.com/facebook/docusaurus/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/docusaurus/commits/v3.10.0/packages/docusaurus) --- updated-dependencies: - dependency-name: "@docusaurus/core" dependency-version: 3.10.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Greptile SummaryDependabot bumps Confidence Score: 3/5Not safe to merge without also bumping all other @docusaurus/* packages to 3.10.0. A P1 version mismatch exists: @docusaurus/core is at 3.10.0 while preset-classic and all devDependency Docusaurus packages stay at 3.9.2. Docusaurus packages must be upgraded together; mixing versions can produce dual installations, React context mismatches, or broken internal APIs that break the docs build. docs/package.json — needs the other @docusaurus/* packages bumped to 3.10.0. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["docs/package.json"] --> B["@docusaurus/core@3.10.0 ✅"]
A --> C["@docusaurus/preset-classic@3.9.2 ⚠️"]
A --> D["@docusaurus/module-type-aliases@3.9.2 ⚠️"]
A --> E["@docusaurus/tsconfig@3.9.2 ⚠️"]
A --> F["@docusaurus/types@3.9.2 ⚠️"]
C --> G["pnpm resolves @docusaurus/core@3.9.2 internally"]
B --> H["Two copies of @docusaurus/core in node_modules"]
G --> H
H --> I["⚠️ Potential React context mismatch / build failure"]
Prompt To Fix All With AIThis is a comment left during a code review.
Path: docs/package.json
Line: 25-26
Comment:
**Mismatched Docusaurus package versions**
`@docusaurus/core` is bumped to `3.10.0` while `@docusaurus/preset-classic`, `@docusaurus/module-type-aliases`, `@docusaurus/tsconfig`, and `@docusaurus/types` all remain at `3.9.2`. Docusaurus packages are released together and are designed to run at the same version — mixing versions can cause duplicate package installations (two copies of `@docusaurus/core` resolved by pnpm: one direct, one pulled by `preset-classic`) and runtime breakage through React context mismatches or mismatched internal APIs. All Docusaurus packages should be upgraded together.
```suggestion
"@docusaurus/core": "3.10.0",
"@docusaurus/preset-classic": "3.10.0",
```
Also update the devDependencies to match:
```
"@docusaurus/module-type-aliases": "3.10.0",
"@docusaurus/tsconfig": "3.10.0",
"@docusaurus/types": "3.10.0",
```
How can I resolve this? If you propose a fix, please make it concise.Reviews (1): Last reviewed commit: "chore(deps): bump @docusaurus/core from ..." | Re-trigger Greptile |
| "@docusaurus/core": "3.10.0", | ||
| "@docusaurus/preset-classic": "3.9.2", |
There was a problem hiding this comment.
Mismatched Docusaurus package versions
@docusaurus/core is bumped to 3.10.0 while @docusaurus/preset-classic, @docusaurus/module-type-aliases, @docusaurus/tsconfig, and @docusaurus/types all remain at 3.9.2. Docusaurus packages are released together and are designed to run at the same version — mixing versions can cause duplicate package installations (two copies of @docusaurus/core resolved by pnpm: one direct, one pulled by preset-classic) and runtime breakage through React context mismatches or mismatched internal APIs. All Docusaurus packages should be upgraded together.
| "@docusaurus/core": "3.10.0", | |
| "@docusaurus/preset-classic": "3.9.2", | |
| "@docusaurus/core": "3.10.0", | |
| "@docusaurus/preset-classic": "3.10.0", |
Also update the devDependencies to match:
"@docusaurus/module-type-aliases": "3.10.0",
"@docusaurus/tsconfig": "3.10.0",
"@docusaurus/types": "3.10.0",
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/package.json
Line: 25-26
Comment:
**Mismatched Docusaurus package versions**
`@docusaurus/core` is bumped to `3.10.0` while `@docusaurus/preset-classic`, `@docusaurus/module-type-aliases`, `@docusaurus/tsconfig`, and `@docusaurus/types` all remain at `3.9.2`. Docusaurus packages are released together and are designed to run at the same version — mixing versions can cause duplicate package installations (two copies of `@docusaurus/core` resolved by pnpm: one direct, one pulled by `preset-classic`) and runtime breakage through React context mismatches or mismatched internal APIs. All Docusaurus packages should be upgraded together.
```suggestion
"@docusaurus/core": "3.10.0",
"@docusaurus/preset-classic": "3.10.0",
```
Also update the devDependencies to match:
```
"@docusaurus/module-type-aliases": "3.10.0",
"@docusaurus/tsconfig": "3.10.0",
"@docusaurus/types": "3.10.0",
```
How can I resolve this? If you propose a fix, please make it concise.There was a problem hiding this comment.
LGTM — straightforward Dependabot minor version bump for docs tooling.
Extended reasoning...
Overview
This PR updates @docusaurus/core from 3.9.2 to 3.10.0 in the /docs directory, touching only docs/package.json and docs/pnpm-lock.yaml. No application or library code is modified.
Security risks
None. This is a documentation site dependency (Docusaurus), not production application code. The upstream release notes include a security-adjacent fix (upgrading serve handler to a secure version), which is a net positive.
Level of scrutiny
Low. This is a Dependabot-generated minor version bump to well-maintained, widely-used documentation infrastructure. Minor version bumps in the Docusaurus ecosystem are generally backward-compatible by convention.
Other factors
No bugs were found by the automated bug hunting system. The PR timeline has no unresolved human reviewer comments. This change is entirely confined to the docs subdirectory and has no impact on the main application codebase.
Bumps @docusaurus/core from 3.9.2 to 3.10.0.
Release notes
Sourced from
@docusaurus/core's releases.... (truncated)
Changelog
Sourced from
@docusaurus/core's changelog.... (truncated)
Commits
0d98888v3.10.04892e7ffeat(core): addfuture.v4.mdx1CompatDisabledByDefaultflag (#11896)543eaebfix(core): fixurl.resolve()Node.js deprecation warning (#11844)1a52592fix(faster): upgrade Rspack, fix Yarn PnP support (#11817)4a0273ffix(create-docusaurus): fix support for TypeScript 6.0 + fix our CI (#11843)f659aeffix(core): upgrade serve handler min version to for upgrade users to a secure...1451780chore(ci): fixes for the npm trusted publishing workflow (#11823)5dff744chore(ci): add Trusted Publishing release workflow through dispatch action (#...29c3b5cfeat(core): Docusaurus Faster is stable + v4 future flag turns it on by defau...2a7f8b9feat(core): promotesiteConfig.storageto stable + add `future.v4.siteStora...Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@docusaurus/coresince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)