Skip to content

chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.11.3 in /plugins/zalouser - #823

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.11.3
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.11.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 14, 2026

Copy link
Copy Markdown
Contributor

Bumps @openclaw/zalouser from 2026.10.9 to 2026.11.3.

Release notes

Sourced from @​openclaw/zalouser's releases.

openclaw 2026.11.3

2026.11.3

Highlights

  • Private task results: Keep private subagent completions out of streamed chat replies. (#188490) Thanks @​fuller-stack-dev.
  • Reliable child-task handoffs: Allow a parent to hand off to replacement work after cancelling a child, without leaving the cancelled child's completion receipt blocking the handoff. (#178893; related #178565) Thanks @​brianmcguire and @​letsc4.
  • Visible tool failures: Report unanswered tool failures instead of silently ending a user-addressed turn as a success. (#182458; related #99645) Authored by @​steipete. Thanks @​rdleclerc.
  • Bounded authentication: Stop stalled provider authentication at the run deadline and propagate cancellation through authentication work. (#189144) Thanks @​amittell.
  • Sandboxed image access: Keep required-sandbox image previews inside allowed folders, even in Full Access mode, while preserving explicit administrator image allowances. (#176203) Thanks @​shakkernerd.
  • Verified workspace connections: Preserve saved node certificate pins when an empty fingerprint is supplied, and verify workspace-transfer certificates before sending credentials or data. (#125646, #190002) Thanks @​wanyongstar and @​avelev99.
  • Faster, responsive Gateway: Reduce startup module-file loading overhead and avoid stalls when abort-command detection encounters long punctuation runs. (#192217, #184433) Thanks @​karkarl, @​RomneyDa, @​LeizhenZhang, and @​obviyus.

Changes

No new configuration options or features.

Fixes

  • Credential isolation: Keep reused and cached plugin results scoped to their connection credentials, and keep other plugins' transport hooks on the provider's origin. (#178444, #177974, #189423) Authored by @​steipete. Thanks @​obviyus.
  • Search and memory credentials: Keep Firecrawl search and scrape keys with their scoped endpoints and embedding credentials with their destination. (#190706, #184966) Thanks @​zhangguiping-xydt and @​eleqtrizit.
  • Credential redaction: Redact inline environment credentials from configuration reads and reflected search credentials from Exa errors. (#190618, #178745) Authored by @​steipete. Thanks @​yetval.
  • Child-process environments: Prevent managed Signal daemons and bundled language servers from inheriting unrelated Gateway secrets. (#179198, #179415) Thanks @​VACInc.
  • Authentication errors: Surface credential-read failures rather than treating them as missing credentials, and reject explicitly selected auth profiles belonging to incompatible providers. (#173970, #181597) Authored by @​steipete. Thanks @​vincentkoc.
  • Channel safety: Keep incoming Twitch IRC content out of parser error logs and require explicit request IDs when multiple Tlon approvals are pending. (#174552, #186243) Authored by @​steipete. Thanks @​mmaps.
  • Scheduled jobs: Handle queued cron storage failures without exiting the Gateway, and clear one-shot cleanup when a job becomes recurring. (#175678, #168985) Authored by @​steipete. Thanks @​yxshee, @​wangmiao0668000666, and @​obviyus.
  • Updates: Let profile-backed updates recognize their own maintenance lock and preserve cancellation when ledger writes are deferred. (#177792, #187998) Thanks @​GrahamMcBain and @​vincentkoc.
  • Update recovery: Recover safely when the initial package-presence check times out, requiring a fresh valid directory identity before replacement and retaining rollback to the original package. (#181906) Authored by @​steipete.
  • Anthropic usage caps: Recognize exhausted plural usage-limit errors without spending the transient rate-limit retry budget. (#176186; related #176179) Thanks @​sunlit-deng and @​blue-dot-1.
  • Terminal sessions: Forward /reset soft to the Gateway instead of hard-resetting the session. (#172431) Thanks @​yetval and @​obviyus.
  • Git recovery: Preserve uncertain command failures during Git repair rather than treating an unconfirmed operation as successful. (#176006) Authored by @​steipete.
  • Memory provider selection: Accept mixed-case none and auto provider values. (#186310) Authored by @​steipete. Thanks @​sagealice2002-dotcom.

Complete contribution record

This audited record covers the complete v2026.11.2..abf11ef015b9d4cdf5b2e6e2a6a84b87c7b8c920 history: 34 in-range PRs + 0 retained seed-only PRs = 34 unique PRs. The generation manifest also supplies direct commits as editorial input; the grouped notes above prioritize user impact.

Pull requests

... (truncated)

Changelog

Sourced from @​openclaw/zalouser's changelog.

Changelog

Release notes: https://docs.openclaw.ai/releases

Each release has its complete changelog below. Audited contribution records are retained separately when available.

... (truncated)

Commits
  • 847611d fix(gateway): settle ACP lifecycle before completion replay
  • dba4a3d fix(update): recover interrupted managed updates on 2026.11.3 (#193884)
  • 70abf44 fix(sessions): isolate private transcript read dispatch
  • d7154a9 test(live): use short random tool probe nonces (#172737)
  • 23fa333 fix(sessions): capture physical read proof after queued admission
  • 3a31314 test(sessions): admit schema probe fixture writes behind maintenance
  • c998519 fix(gateway): keep idle replay lookup off history lane
  • 3ac9ee0 fix(gateway): replay consumed collected inputs after idle
  • 6de33ec fix(sessions): avoid worker OOM during large transcript index repair
  • fd8dd65 docs: check hotfix ledger completeness at release closeout (#196355)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 14, 2026
@clawsweeper

clawsweeper Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Nov 14, 2026
@clawsweeper

clawsweeper Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge.

What this changes

Updates 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.

  • Before: The materializer falls back to 2026.10.9.
  • After: The materializer falls back to 2026.11.3.

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) Existing-state compatibility remains unproven, source attribution is incorrect, and the recorded host prerequisite remains unresolved.
Proof confidence 🧂 unranked krab (1/6) This bot-authored fixture refresh is outside the general contributor proof gate, but no existing-state upgrade evidence covers the changed credentials namespace operations, legacy credentials files, or direct-message session-key migration.
Patch quality 🦪 silver shellfish (2/6) 1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: No · Fix scope: Complete
User problem: Crabpot’s frozen fallback trails the published Zalo Personal plugin release.
Reason: As proposed, this repeats an unqualified fallback refresh that maintainers already deferred pending host promotion; no package-specific benefit establishes an exception.

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
Reviewed head: b73b75a0c79e04648f23e1c010d13dae4b36bd1c

Before merge

  • Update the source references alongside the fallback version (P2) - The selected registry manifest and archive omit gitHead, but the shim sourceRef and manifest source.ref still identify prepared source for 2026.10.9. When 2026.11.3 is materialized, its version now matches the shim, so readPackagePayloadSourceRef and packageEvidenceRef generate source links using that old SHA. Verify the prepared source through publication qualification and update both references with the fallback.
  • Resolve merge risk - Before inclusion, the maintainer must complete the eligible-host qualification and promotion tracked in Qualify a newer Default Track host before refreshing official plugin fallbacks #780; native admission on the current 2026.10.6 host skips the selected package.
  • Product: not worth merging - As proposed, this repeats an unqualified fallback refresh that maintainers already deferred pending host promotion; no package-specific benefit establishes an exception.
  • Add data-model compatibility proof - The review found that existing stored data may not work after upgrade. Show that existing data still loads and works with this change.
  • Explain or restore the original intent of Fallback artifact and source pairing - aa34909: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 paired the selected fallback artifacts with verified publication-source references.

Findings

  • [P2] Update the source references alongside the fallback version — plugins/zalouser/package.json:7

Provenance

Tests

  • Missing end-to-end proof: Provide an existing-state upgrade run covering the changed credential-store access and Doctor credential/session migrations, with settings and valid data preserved and secrets redacted.
Agent review details

How this fits together

Crabpot 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]
Loading

Technical review

Best 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:

  • [P2] Update the source references alongside the fallback version — plugins/zalouser/package.json:7
    The selected registry manifest and archive omit gitHead, but the shim sourceRef and manifest source.ref still identify prepared source for 2026.10.9. When 2026.11.3 is materialized, its version now matches the shim, so readPackagePayloadSourceRef and packageEvidenceRef generate source links using that old SHA. Verify the prepared source through publication qualification and update both references with the fallback.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.97

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 90b39250dd03.

Merge-risk options

Maintainer options:

  1. Defer the fallback refresh (recommended)
    Retain 2026.10.9 while the existing immutable-host qualification and promotion work completes.
  2. Qualify a coherent host and package pair
    Complete the existing host prerequisite before including the selected fallback in a verified fixture refresh.

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

Likely related people:

  • Peter Steinberger: Raw commit aa34909 adds plugins/zalouser/package.json:15 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: aa349094d146; files: plugins/zalouser/package.json)
  • Vincent Koc: Raw commit 614b320 adds plugins/zalouser/package.json:13 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 614b3209ea42; files: plugins/zalouser/package.json)

Preflight source

Source 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 cluster

Relationship: partial_overlap
Canonical: #780
Summary: The host-qualification issue owns the shared prerequisite; this PR additionally introduces its own source-attribution mismatch.

Members:

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Labels

Label changes:

  • add P3: Routine fixture maintenance with a bounded reporting defect and no established urgent user regression.
  • add merge-risk: 🚨 compatibility: The selected artifact requires native plugin API >=2026.11.3, while the qualified host remains 2026.10.6.
  • add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦪 silver shellfish.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Label justifications:

  • P3: Routine fixture maintenance with a bounded reporting defect and no established urgent user regression.
  • merge-risk: 🚨 compatibility: The selected artifact requires native plugin API >=2026.11.3, while the qualified host remains 2026.10.6.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦪 silver shellfish.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action.

Rating scale

6/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.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 14, 2026, 4:28 AM ET / 09:28 UTC.

@dependabot @github

dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #852.

@dependabot dependabot Bot closed this Nov 19, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.11.3 branch November 19, 2026 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants