chore(deps): bump @docusaurus/core from 3.10.0 to 3.10.1#62
chore(deps): bump @docusaurus/core from 3.10.0 to 3.10.1#62dependabot[bot] wants to merge 1 commit intodevelopfrom
Conversation
Bumps [@docusaurus/core](https://github.com/facebook/docusaurus/tree/HEAD/packages/docusaurus) from 3.10.0 to 3.10.1. - [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.1/packages/docusaurus) --- updated-dependencies: - dependency-name: "@docusaurus/core" dependency-version: 3.10.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
🤖 Augment PR SummarySummary: This PR updates the Docusaurus core dependency to the latest patch release. Changes:
Why: To pick up Docusaurus v3.10.1 patch fixes (notably a bundler/webpackbar bug fix mentioned in the upstream release notes). Technical Notes:
🤖 Was this summary useful? React with 👍 or 👎 |
| }, | ||
| "dependencies": { | ||
| "@docusaurus/core": "^3.10.0", | ||
| "@docusaurus/core": "^3.10.1", |
There was a problem hiding this comment.
@docusaurus/core is bumped to ^3.10.1, but other @docusaurus/* deps remain at ^3.10.0; in package-lock.json this results in both @docusaurus/core@3.10.1 and nested @docusaurus/core@3.10.0 installs under plugins/preset. Mixed core versions can cause subtle build/runtime issues in Docusaurus, so consider keeping the Docusaurus package versions in sync.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
|
Looks like @docusaurus/core is up-to-date now, so this is no longer needed. |



Bumps @docusaurus/core from 3.10.0 to 3.10.1.
Release notes
Sourced from @docusaurus/core's releases.
Changelog
Sourced from @docusaurus/core's changelog.
Commits
41c1a45v3.10.1d4164aechore: cherry-pick commits for v3.10.1 patch release (#11982)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)