Repository navigation
chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.10.10 in /plugins/zalouser - #743
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@openclaw/zalouser](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.10.10. - [Release notes](https://github.com/openclaw/openclaw/releases) - [Changelog](https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md) - [Commits](openclaw/openclaw@v2026.10.9...v2026.10.10) --- updated-dependencies: - dependency-name: "@openclaw/zalouser" dependency-version: 2026.10.10 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: needs real behavior proof before merge. What this changesUpdates the Zalo Personal fixture fallback to @openclaw/zalouser 2026.10.10, including its lockfile and bundled TypeBox version. Example: The configured Zalo Personal npm tag is unavailable.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness⛔ Blocked before merge - 7 items remain Keep this PR open: main still pins 2026.10.9, and the update introduces incorrect source attribution that needs repair before merge. Priority: P3 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherCrabpot materializes configured plugin fixtures, inspects their contracts against an OpenClaw host, and produces compatibility reports with upstream source links. flowchart LR
A[Fixture manifest] --> C[Package materializer]
B[Fallback pin and lock] --> C
C --> D[Plugin payload]
D --> E[Compatibility inspector]
E --> F[Reports and source links]
Technical reviewBest possible solution: Pair the fallback with its verified prepared source in both existing references and qualify the changed credential and migration paths without changing moving tracks or the host pin. Do we have a high-confidence way to reproduce the issue? The attribution defect follows directly from the inspected archive lacking gitHead and the report owner selecting the unchanged source reference when its version matches the new pin; no target code was executed. Is this the best way to solve the issue? Updating the existing fallback is consistent with established maintenance, but the package pin alone is incomplete because attribution deliberately depends on its paired source reference. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 497e477988b6. Merge-risk optionsMaintainer options:
Provenance checked
TestingProof path: in-process harness. SecurityNeeds attention: Archive integrity and package identity match, but the changed credential-authority path needs final-write evidence. EvidenceSecurity concerns:
What I checked:
Likely related people:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed November 6, 2026, 4:30 AM ET / 09:30 UTC. |
|
Superseded by #767. |
Bumps @openclaw/zalouser from 2026.10.9 to 2026.10.10.
Release notes
Sourced from @openclaw/zalouser's releases.
... (truncated)
Changelog
Sourced from @openclaw/zalouser's changelog.
... (truncated)
Commits
7dc3350fix(process): share inherited process lineage across module copies81df37dtest(update): give Doctor receipt retention a realistic deadline0c755e0fix(claude-cli): keep the parent session when completions mediate file tools914d1aefix(agents): keep the portal tool declared on non-owner turnsd75937cfix(agents): keep CLI completion tool catalogs stable (#176892)465b0b7ci(release): reclaim hosted runner disk before Docker and live lanesd562323fix(file-transfer): share one workspace command import between memory and skills8c275c6test(gateway): wait out Codex's unload confirmation window before physical exit216b1dffix(sqlite): wait for a cold database turn before the shared worker open queuef6a0243test(ui): match packaged Workboard mock Gateway to the served buildDependabot 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)