Skip to content

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

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps @openclaw/zalouser from 2026.10.9 to 2026.11.2.

Release notes

Sourced from @​openclaw/zalouser's releases.

openclaw 2026.11.2

OpenClaw v2026.11.2

166 commits · 113 pull requests · 64 contributors

Changes included in this release

The release notes and changelog contain the same content, presented in two formats:

Thanks

@​1052326311 @​651juan @​abacha @​amittell @​anmol0b @​beebee @​cestercian @​DasX @​davidcittadini @​DonnieFi @​eliavb43 @​etzelm @​fhgffy @​Finn763 @​fuller-stack-dev @​g62nkcx4q7-wq @​galiniliev @​hannesrudolph @​holgergruenhagen @​HootRock @​huyengiang101086-spec @​IWhatsskill @​javiermv @​joeykrug @​joshavant @​Kimiyu-186 @​LachieFREEDOM @​LeizhenZhang @​Leon-SK668 @​LiuwqGit @​Marvinthebored @​masatohoshino @​mnowrot @​Nickfost @​nxmxbbd @​obviyus @​Oldrich333 @​OliPlus @​Patrick-Erichsen @​Peetiegonzalez @​pgondhi987 @​potoior @​RomneyDa @​Satoshi-Kusumoto @​SebTardif @​sem00-ft @​shakkernerd @​Solvely-Colin @​steipete @​sukhdeepjohar @​sunlit-deng @​SunnyShu0925 @​TameTheGame @​theimmortal68 @​ullrichg13 @​VACInc @​vincentkoc @​wangmiao0668000666 @​wr-web @​YangManBOBO @​yetval @​Yolo521-bot @​yousan @​zhangguiping-xydt

Release verification

openclaw 2026.11.1

2026.11.1

Highlights

Changes

... (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
  • b556fdf test: keep archive lifecycle fixtures out of age maintenance
  • aa20474 test: wait for explicit native catalog discovery readiness
  • f46f008 test(macos): synchronize stalled navigation and report stop state
  • 31efa7a test: keep simulated Darwin listeners outside Linux client ports
  • b4c7fe5 test: clean up late durability dispatches after RPC failure
  • 1a6914c test: distinguish CLI completion reply from early child mention
  • 46bcb1c test: pass voice fallback agent runtime in correct slot
  • 62e4cc1 test: establish legacy exec dispatch before timeout
  • 9cfe377 test: use explicit boolean coercion in durability diagnostics
  • 5534c90 test: format durability phase diagnostics
  • 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.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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 11, 2026
@clawsweeper

clawsweeper Bot commented Nov 11, 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. merge-risk: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Nov 11, 2026
@clawsweeper

clawsweeper Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs real behavior proof before merge.

What this changes

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

  • Before: Crabpot requests @openclaw/zalouser@2026.10.9.
  • After: Crabpot requests @openclaw/zalouser@2026.11.2.

Review scores

Measure Result What it means
Overall readiness 🦪 silver shellfish (2/6) A small dependency refresh with a definite attribution defect, an established host prerequisite, and limited evidence for changed credential persistence and migration behavior.
Proof confidence 🦪 silver shellfish (2/6) Real behavior proof is necessary before merge. See Before merge.
Patch quality 🦐 gold shrimp (3/6) Security review found an item that needs attention.

Product

Kind: Maintenance · Worth it: No · Fix scope: Complete
User problem: Crabpot's pinned fallback trails the published Zalo Personal package.
Reason: As proposed, this repeats the host incompatibility behind the recorded deferral of #767; reconsideration already has a defined qualification path.

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
Reviewed head: 85b5836be965bb5f523dc4b22489fb5e8ad70188

Before merge

  • Add real behavior proof - Authority-chain proof required: show that a current QR login can persist credentials and that a superseded or revoked login cannot write after awaited work through the real V2 store and persistence owner. The passing isolated fixture job declares compatibility inspection rather than that scenario; its artifact and logs could not be inspected because the environment blocked their Azure download host, which is not a contributor defect. Redact credentials and non-public endpoints from supplied traces. After adding proof, update the PR body, then request a new review with @clawsweeper re-review. The PR author or someone with repository write access can request it.
  • Update the source references alongside the fallback version (P2) - The 2026.11.2 registry manifest and archive omit gitHead, but both the shim sourceRef and manifest source.ref still identify the prepared 2026.10.9 source. When this payload is materialized, readPackagePayloadSourceRef now sees payloadVersion equal to pinnedVersion and packageEvidenceRef returns that old SHA, generating source links for the wrong artifact. Verify the prepared source from publication qualification, update both references, and refresh the affected report expectations as required by AGENTS.md.
  • Resolve security concern: Verify login authority at credential persistence - The selected archive transfers assertCurrent from individual credential operations into openKeyedStoreV2 construction and removes older-store paths; inspection found no concrete bypass, so this is an unresolved qualification concern rather than a claimed vulnerability.
  • Resolve merge risk - The maintainer should defer inclusion until the eligible immutable host is qualified and promoted through Qualify a newer Default Track host before refreshing official plugin fallbacks #780; the current 2026.10.6 host rejects the selected package's native API floor.
  • Resolve merge risk - The PR owner must establish that the changed credential-store authority handoff rejects superseded or revoked logins before the final persisted write.
  • Product: not worth merging - As proposed, this repeats the host incompatibility behind the recorded deferral of chore(deps): bump @openclaw/zalouser from 2026.10.9 to 2026.11.1 in /plugins/zalouser #767; reconsideration already has a defined qualification path.
  • 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 2026.10.9 fallback with verified prepared-source references while retaining the separately qualified host.

Findings

  • [P2] Update the source references alongside the fallback version — plugins/zalouser/package.json:7
  • [medium] Verify login authority at credential persistence — plugins/zalouser/package.json:7

Provenance

Tests

  • Missing end-to-end proof: No inspected evidence establishes current-versus-superseded login behavior at credential persistence or an existing-state upgrade through the changed Doctor migrations.
Agent review details

How this fits together

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

Technical review

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

  • [P2] Update the source references alongside the fallback version — plugins/zalouser/package.json:7
    The 2026.11.2 registry manifest and archive omit gitHead, but both the shim sourceRef and manifest source.ref still identify the prepared 2026.10.9 source. When this payload is materialized, readPackagePayloadSourceRef now sees payloadVersion equal to pinnedVersion and packageEvidenceRef returns that old SHA, generating source links for the wrong artifact. Verify the prepared source from publication qualification, update both references, and refresh the affected report expectations as required by AGENTS.md.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.96

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 update (recommended)
    Retain 2026.10.9 while the existing host-qualification work completes.
  2. Qualify a coherent host and package pair
    Complete the recorded host promotion requirements, repair source attribution, and establish credential-authority and existing-state compatibility through the real owners.

Provenance checked

Testing

Proof path: in-process harness.

Security

Needs attention: Artifact integrity matches, but the changed credential-authority handoff still needs final-write qualification.

Evidence

Security concerns:

  • [medium] Verify login authority at credential persistence — plugins/zalouser/package.json:7
    The selected archive transfers assertCurrent from individual credential operations into openKeyedStoreV2 construction and removes older-store paths; inspection found no concrete bypass, so this is an unresolved qualification concern rather than a claimed vulnerability.
    Confidence: 0.93

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: This fallback update shares the canonical host-qualification prerequisite but also 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 package requires native plugin API >=2026.11.2 while the qualified host remains 2026.10.6.
  • add merge-risk: 🚨 security-boundary: The selected artifact changes how current-login authority reaches persisted credential operations.
  • add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🦐 gold shrimp.
  • add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Label justifications:

  • P3: Routine fixture maintenance with a bounded reporting defect and no established urgent user regression.
  • merge-risk: 🚨 compatibility: The selected package requires native plugin API >=2026.11.2 while the qualified host remains 2026.10.6.
  • merge-risk: 🚨 security-boundary: The selected artifact changes how current-login authority reaches persisted credential operations.
  • rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🦐 gold shrimp.
  • status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

  • Add final-effect proof that current login authority permits credential persistence and superseded or revoked authority prevents it before storage I/O.

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 11, 2026, 4:30 AM ET / 09:30 UTC.

@steipete

Copy link
Copy Markdown
Contributor

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.

@steipete steipete closed this Nov 14, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

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 @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

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. merge-risk: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant