chore(deps): bump @docusaurus/preset-classic from 3.9.2 to 3.10.0 in /docs#340
Conversation
Bumps [@docusaurus/preset-classic](https://github.com/facebook/docusaurus/tree/HEAD/packages/docusaurus-preset-classic) 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-preset-classic) --- updated-dependencies: - dependency-name: "@docusaurus/preset-classic" 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 SummaryThis PR bumps Confidence Score: 5/5Safe to merge; the version mismatch is a housekeeping concern that won't break builds. The only finding is a P2 style concern — the remaining Docusaurus packages should ideally be bumped in the same PR for consistency, but pnpm resolves the dual-version scenario correctly and the docs site will continue to build and run. docs/package.json — the @docusaurus/core and devDependency versions should be aligned with preset-classic@3.10.0. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["docs/package.json"] -->|"direct dep: @docusaurus/core@3.9.2"| B["@docusaurus/core@3.9.2"]
A -->|"direct dep: @docusaurus/preset-classic@3.10.0"| C["@docusaurus/preset-classic@3.10.0"]
C -->|"peer dep resolved via lockfile"| D["@docusaurus/core@3.10.0"]
A -->|"devDeps unchanged"| E["@docusaurus/module-type-aliases@3.9.2\n@docusaurus/tsconfig@3.9.2\n@docusaurus/types@3.9.2"]
B -.->|"⚠️ dual install"| D
Prompt To Fix All With AIThis is a comment left during a code review.
Path: docs/package.json
Line: 25-26
Comment:
**Docusaurus package version mismatch**
`@docusaurus/preset-classic` is now at `3.10.0` while `@docusaurus/core` (line 25), `@docusaurus/module-type-aliases`, `@docusaurus/tsconfig`, and `@docusaurus/types` (devDependencies) are all still pinned at `3.9.2`. The lockfile confirms pnpm ends up installing **two copies** of `@docusaurus/core` — `3.9.2` for the direct dependency and `3.10.0` pulled in by the preset. Docusaurus packages are designed to be upgraded together; consider bumping all `@docusaurus/*` packages to `3.10.0` for consistency.
```suggestion
"@docusaurus/core": "3.10.0",
"@docusaurus/preset-classic": "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/preset-cla..." | Re-trigger Greptile |
| "@docusaurus/core": "3.9.2", | ||
| "@docusaurus/preset-classic": "3.9.2", | ||
| "@docusaurus/preset-classic": "3.10.0", |
There was a problem hiding this comment.
Docusaurus package version mismatch
@docusaurus/preset-classic is now at 3.10.0 while @docusaurus/core (line 25), @docusaurus/module-type-aliases, @docusaurus/tsconfig, and @docusaurus/types (devDependencies) are all still pinned at 3.9.2. The lockfile confirms pnpm ends up installing two copies of @docusaurus/core — 3.9.2 for the direct dependency and 3.10.0 pulled in by the preset. Docusaurus packages are designed to be upgraded together; consider bumping all @docusaurus/* packages to 3.10.0 for consistency.
| "@docusaurus/core": "3.9.2", | |
| "@docusaurus/preset-classic": "3.9.2", | |
| "@docusaurus/preset-classic": "3.10.0", | |
| "@docusaurus/core": "3.10.0", | |
| "@docusaurus/preset-classic": "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:
**Docusaurus package version mismatch**
`@docusaurus/preset-classic` is now at `3.10.0` while `@docusaurus/core` (line 25), `@docusaurus/module-type-aliases`, `@docusaurus/tsconfig`, and `@docusaurus/types` (devDependencies) are all still pinned at `3.9.2`. The lockfile confirms pnpm ends up installing **two copies** of `@docusaurus/core` — `3.9.2` for the direct dependency and `3.10.0` pulled in by the preset. Docusaurus packages are designed to be upgraded together; consider bumping all `@docusaurus/*` packages to `3.10.0` for consistency.
```suggestion
"@docusaurus/core": "3.10.0",
"@docusaurus/preset-classic": "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 a docs-only dependency.
Extended reasoning...
Overview
This PR bumps @docusaurus/preset-classic from 3.9.2 to 3.10.0 in the /docs directory. Only docs/package.json and docs/pnpm-lock.yaml are modified — no application code is touched.
Security risks
None. This is a documentation site dependency with no access to production systems, auth, or sensitive data. The 3.10.0 release notes include a fix that upgrades the serve handler to a more secure version, making this bump slightly beneficial from a security standpoint.
Level of scrutiny
Low. Minor version bumps to Docusaurus in a docs-only subdirectory are routine and low-risk. The change is mechanical and generated by Dependabot.
Other factors
No bugs were found by the bug hunting system. No prior reviews on this PR. The Dependabot compatibility score badge is present, and the bump is within the same major version (3.x), so breaking changes are not expected.
Bumps @docusaurus/preset-classic from 3.9.2 to 3.10.0.
Release notes
Sourced from
@docusaurus/preset-classic's releases.... (truncated)
Changelog
Sourced from
@docusaurus/preset-classic's changelog.... (truncated)
Commits
0d98888v3.10.01451780chore(ci): fixes for the npm trusted publishing workflow (#11823)5dff744chore(ci): add Trusted Publishing release workflow through dispatch action (#...bca9ce7chore: release v3.9.2 (#11491)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@docusaurus/preset-classicsince 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)