chore(deps): bump openclaw from 2026.5.7 to 2026.6.10#31
chore(deps): bump openclaw from 2026.5.7 to 2026.6.10#31dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [openclaw](https://github.com/openclaw/openclaw) from 2026.5.7 to 2026.6.10. - [Release notes](https://github.com/openclaw/openclaw/releases) - [Commits](openclaw/openclaw@v2026.5.7...v2026.6.10) --- updated-dependencies: - dependency-name: openclaw dependency-version: 2026.6.10 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2aec6d53e9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "integrity": "sha512-76wdkrmfXfqGjueGgnb45ITPyUi1ycZ4IHgC2bhPDUfWHklY/q3MdLOAB+TF1e6xfl8NxNY0ZYaPCFNWSsw3Ug==", | ||
| "dev": true, | ||
| "node_modules/openclaw/node_modules/@types/retry": { | ||
| "version": "0.12.5", |
There was a problem hiding this comment.
Regenerate the invalid nested lock entries
This lock entry resolves @types/retry to 0.12.5, but the same updated OpenClaw tree declares p-retry's dependency as the exact version 0.12.0 at package-lock.json:3566; it also resolves tar to 7.5.16 while @openclaw/fs-safe requests exact 7.5.13 at package-lock.json:1401. I checked the package-lock tree with the documented npm ls --package-lock-only --all options, and npm exits with ELSPROBLEMS for these invalid packages, so dependency-tree validation fails even before tests run. Regenerate or pin the nested entries to versions that satisfy the exact constraints before landing the bump.
Useful? React with 👍 / 👎.
Bumps openclaw from 2026.5.7 to 2026.6.10.
Release notes
Sourced from openclaw's releases.
... (truncated)
Commits
aa69b12docs(changelog): refresh 2026.6.10 notes3521a01chore(release): prepare 2026.6.10 stable5ed8323test(e2e): refresh docker setup fixturee42b914fix(ci): keep release branch CI shard bundles compatible51459a4docs(changelog): include provider onboarding fix8b5527bfix(onboard): refresh provider plugin registry after setup installs (#95792)87b40c7test(release): align beta2 validation expectationsb8108e4test(telegram): add progress preview helperdec86fechore(release): refresh beta2 validation baselinesa2e5553test(agents): cover fallback probe attempt positionInstall script changes
This version modifies
preparescript that runs during installation. Review the package contents before updating.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)You can disable automated security fix PRs for this repo from the Security Alerts page.