Repository navigation
chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.11.1 in /plugins/zalouser - #767
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@openclaw/zalouser](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.1. - [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.1) --- updated-dependencies: - dependency-name: "@openclaw/zalouser" dependency-version: 2026.11.1 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 changesUpdates the Zalo Personal fixture fallback to @openclaw/zalouser 2026.11.1 and refreshes its lockfile metadata. Example: The configured Zalo Personal npm tag is unavailable.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness⛔ Blocked before merge - 6 items remain Keep this PR open: main still uses 2026.10.9, and the update would attribute the new fallback artifact to the previous release’s source. Priority: P3 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherCrabpot materializes configured plugin packages, inspects their compatibility with an OpenClaw host, and generates 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 verified prepared-source references and qualify its credential and migration behavior while preserving existing track selectors and host ownership. Do we have a high-confidence way to reproduce the issue? The reporting defect follows directly from the verified archive lacking gitHead and the report owner selecting the old source reference when the payload matches the updated pin; no target code was executed. Is this the best way to solve the issue? Updating the existing fallback is appropriately scoped, but changing its version without its paired source references breaks the established attribution contract. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 4907a46607cc. Merge-risk optionsMaintainer options:
Provenance checked
TestingProof path: in-process harness. SecurityNeeds attention: Artifact integrity matches, but the changed credential-authority boundary 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 8, 2026, 4:28 AM ET / 09:28 UTC. |
|
Closing this The Default Track pin selects OpenClaw Reconsider after an eligible immutable host completes full-corpus and three-platform qualification, its source pin is promoted through review, and the exact package cohort is qualified. Tracked in #780. Publication provenance alone is not runtime compatibility evidence. |
|
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.1.
Release notes
Sourced from @openclaw/zalouser's releases.
... (truncated)
Changelog
Sourced from @openclaw/zalouser's changelog.
... (truncated)
Commits
4ffdd20test(release): supply the state script to manifest writer proofsd285b6aci(release): route FRV state operations to admitted toolingb8fbe16test: widen hosted cold-start limits for durability and voice-call proofsec5d8d2test(workers): format the aged memo clock import3a4983efix(test): report HTTP status when cache probes failc16f7a9test(workers): age fixture ctimes for memo reuse proofsef14ea4chore(release): attest 2026.11.1 candidate5a44cd1fix(release): shorten branch push preflight (#188743)adbc189refactor: split oversized backport modulesea0a7c8fix(agents): honor user constraints during response recoveryDependabot 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)