Repository navigation
chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.11.2 in /plugins/zalouser - #801
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@openclaw/zalouser](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.2. - [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.2) --- updated-dependencies: - dependency-name: "@openclaw/zalouser" dependency-version: 2026.11.2 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: needs real behavior proof before merge. What this changesThis PR updates the Zalo Personal fixture fallback to @openclaw/zalouser 2026.11.2 and refreshes its lock metadata. Example: The configured npm tag is unavailable and Crabpot selects the Zalo Personal fallback.
Review scores
ProductKind: Maintenance · Worth it: No · Fix scope: Complete Merge readiness⛔ Blocked before merge - 8 items remain Keep this PR open: main still uses 2026.10.9, and repository policy permits no cleanup close here; the update needs corrected source attribution and must respect the recorded host-qualification prerequisite. Priority: P3 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherCrabpot resolves fixture packages from configured npm tracks or pinned fallbacks, materializes them for compatibility inspection, and produces reports with artifact and source attribution. 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 update the exact package, lock, verified prepared-source references, and matching report evidence together. Do we have a high-confidence way to reproduce the issue? Source establishes that a 2026.11.2 payload without gitHead now matches the shim version and receives the unchanged 2026.10.9 source reference; no target code was run. Is this the best way to solve the issue? The version and integrity edits are consistent with npm metadata, but a complete fixture refresh also needs verified artifact-source pairing and the already-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: in-process harness. SecurityNeeds attention: Artifact integrity matches, but the changed credential-authority handoff still needs final-write qualification. 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. 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:
Rank-up movesOptional improvements that raise the rating; they are not merge blockers.
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 11, 2026, 4:30 AM ET / 09:30 UTC. |
|
Closing this unqualified fallback update pending #780. The exact registry manifest requires plugin API >=2026.11.2, while Crabpot’s qualified Default Track host remains 2026.10.6. Native host admission skips this incompatible package; a green report against a moving artifact does not qualify this fallback. After the separately owned host qualification/promotion, the cohort can be refreshed together with verified publication-source references. The current fallback and source pins are retained. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @openclaw/zalouser from 2026.10.9 to 2026.11.2.
Release notes
Sourced from @openclaw/zalouser's releases.
... (truncated)
Changelog
Sourced from @openclaw/zalouser's changelog.
... (truncated)
Commits
b556fdftest: keep archive lifecycle fixtures out of age maintenanceaa20474test: wait for explicit native catalog discovery readinessf46f008test(macos): synchronize stalled navigation and report stop state31efa7atest: keep simulated Darwin listeners outside Linux client portsb4c7fe5test: clean up late durability dispatches after RPC failure1a6914ctest: distinguish CLI completion reply from early child mention46bcb1ctest: pass voice fallback agent runtime in correct slot62e4cc1test: establish legacy exec dispatch before timeout9cfe377test: use explicit boolean coercion in durability diagnostics5534c90test: format durability phase diagnosticsDependabot 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)