Repository navigation
chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.11.3 in /plugins/zalouser - #823
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@openclaw/zalouser](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.3. - [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.11.3) --- updated-dependencies: - dependency-name: "@openclaw/zalouser" dependency-version: 2026.11.3 dependency-type: direct:production update-type: version-update:semver-minor ... 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: blocked before merge. What this changesUpdates the Zalo Personal fixture fallback from @openclaw/zalouser 2026.10.9 to 2026.11.3. Example: The configured npm tag cannot be resolved for zalouser.
Review scores
ProductKind: Maintenance · Worth it: No · Fix scope: Complete Merge readiness⛔ Blocked before merge - 5 items remain Keep open under the repository’s conservative close policy: main still pins 2026.10.9, and this PR introduces incorrect source attribution while the newer-host prerequisite remains unresolved. Priority: P3 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherCrabpot resolves plugin fixtures from moving npm tags or pinned fallbacks, inspects them against its qualified OpenClaw host, and generates compatibility reports with source links. flowchart LR
A[Fixture manifest] --> B[Package resolver]
C[Fallback shim] --> B
B --> D[Npm artifact]
D --> E[Host compatibility inspection]
E --> F[Reports and source links]
Technical reviewBest possible solution: Retain the reviewed fallback until host qualification completes, then refresh the exact artifact, lock, verified source references, and compatibility evidence together. Do we have a high-confidence way to reproduce the issue? Source and archive inspection establish that a 2026.11.3 payload without gitHead matches the updated shim version and receives the retained 2026.10.9 source reference; no target code was executed. Is this the best way to solve the issue? The package and integrity edits match publication metadata, but a complete refresh must preserve verified artifact-source pairing and satisfy the recorded host prerequisite. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 90b39250dd03. Merge-risk optionsMaintainer options:
Provenance checked
TestingProof path: none. SecurityNone. EvidenceWhat 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. Root-cause clusterRelationship: Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. 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 14, 2026, 4:28 AM ET / 09:28 UTC. |
|
Superseded by #852. |
Bumps @openclaw/zalouser from 2026.10.9 to 2026.11.3.
Release notes
Sourced from @openclaw/zalouser's releases.
... (truncated)
Changelog
Sourced from @openclaw/zalouser's changelog.
... (truncated)
Commits
847611dfix(gateway): settle ACP lifecycle before completion replaydba4a3dfix(update): recover interrupted managed updates on 2026.11.3 (#193884)70abf44fix(sessions): isolate private transcript read dispatchd7154a9test(live): use short random tool probe nonces (#172737)23fa333fix(sessions): capture physical read proof after queued admission3a31314test(sessions): admit schema probe fixture writes behind maintenancec998519fix(gateway): keep idle replay lookup off history lane3ac9ee0fix(gateway): replay consumed collected inputs after idle6de33ecfix(sessions): avoid worker OOM during large transcript index repairfd8dd65docs: check hotfix ledger completeness at release closeout (#196355)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)