Skip to content

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

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps @openclaw/zalouser from 2026.10.9 to 2026.10.10.

Release notes

Sourced from @​openclaw/zalouser's releases.

openclaw 2026.10.10

OpenClaw v2026.10.10

4,825 commits · 3,028 pull requests · 454 contributors

Changes included in this release

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

Thanks

@​3n8 @​555aaditya @​5jrfrbd6z9-spec @​609NFT @​67-luck @​888achtachtacht-commits @​8bitsforge @​A-Raphie @​aaa2015 @​abacha @​Abhishek-B-R @​acedatacloud-dev @​actwebmaster @​adamdksaad-ops @​adeepn @​adembektas @​agierror @​aleps001 @​alexm @​alexph-dev @​Alix-007 @​alkor2000 @​altaywtf @​alter @​AmelioMansour @​amirarenco-create @​amittell @​amueller80 @​amyduquette @​andrewbowlds @​andris9 @​aniruddhaadak80 @​anmol0b @​anyech @​areslp @​arhxam @​arquiteto-raiz @​art22s @​arthur-drozdov @​ArthurNie @​ashukla147 @​AVCarp @​AXEG0 @​ayaangazali @​Ayushdevo @​bajiaoshan @​Bartok9 @​beenhero @​benjaml4 @​beru-ant-king @​bitfroest @​bjesuiter @​blance2599 @​bluet @​boeingchoco @​brandon-julio-t @​brianmcguire @​bricelb @​brokemac79 @​bulingbuling688 @​camerono @​Canvinus @​Card4Philippe @​carlopignatari-boop @​CassieMei @​castigiova @​chelsealong @​chitowntony @​chughtapan @​clarkbw @​clawSean @​clement-paradex @​cnnceart @​crwohlfeil @​Cyb3rb1ade @​dabase @​daddyclint82 @​DagenGuo @​dankarization @​DarkJuanFra @​davidcittadini @​davidgrinc @​davidjoshua7692-code @​deepujain @​demos-ra @​desksk @​dh-js @​Dhotei @​diegoln @​digitalfrost84 @​dineshsuthar123 @​diregoblin @​dmorn @​dmsrg399 @​DonnieFi @​DrDanielSingleton @​drewjocham @​dsantoreis @​dtump @​duardor968 @​duyufansh2008 @​dwalthour @​dwc1997 @​dwty11 @​eightHundreds @​eiriktorheim @​eleqtrizit @​eli-pavlov @​eliavb43 @​elikampf @​Embracex1998 @​EmeraldPi @​EndeavorPioneer @​engagepy @​enki @​ensignwesley @​ericcaiwx-star @​ericcurtin @​erlightbourn-source @​etzelm @​EvolveAegis @​exGeni @​exisz @​ExoHumann @​fanmeng-felix @​fbuechler @​fede-kamel @​feiniaoivp @​fhgffy @​forrystudio @​franssauermann @​freeqaz @​fuller-stack-dev @​funnysubaru @​gdpu11 @​geekforlife @​giodl73 @​giodl73-repo @​git-larry-roots @​gkoch02 @​Glukmann @​GoldArowana @​gorkem2020 @​goslingmanagment @​gregbond @​Grynn @​hamedshehab @​hannesrudolph @​hannnnn-l @​harjothkhara @​harshitgavita-07 @​Hawk5150 @​Hawkeye2611 @​hbgangcn1 @​Heighte @​hengtested-design @​HerbertHuerto @​HeZ2z @​hidaba @​hippoley @​holgergruenhagen @​homeworld520 @​Honghe @​hoobnn @​HootRock @​htuyer121 @​hugenshen @​husodrn46 @​HussonT @​imadal1n @​IndySweeney @​Iolaum @​Irish-Joseph @​itanyplus @​IWhatsskill @​jackylecalvez2 @​jacobtomlinson @​jaisummagithub @​jalehman @​jamesachurchill @​JamesY023 @​jamiezigelbaum @​jason-allen-oneal @​JasonBuildAI @​jaxonparrott @​jayswu @​jb510 @​Jeehut @​jewseppi @​JFLeonM @​Jimmy-xuzimo @​jimmy00415 @​jimmypuckett @​jjgao @​jjjhenriksen @​jlapenna @​johan-eilertsen @​jonathanlindsay @​jondihaynes @​joshavant @​joshpetras @​jsf9789 @​julianloperar @​karaaslanz @​KarimVKarmali @​keiseisales @​KenYounge @​keshavbotagent @​KhanCold @​Kimiyu-186 @​kir1ll @​kiranvk-2011 @​kitiyeung @​kobihikri @​kqtxmaster-boop @​KrasimirKralev @​krell11 @​kseczhouyb @​L4XB @​lakemike @​lator57-gif @​leapdragon @​legend91019 @​Leon-SK668 @​libaojiang @​licheer-zte @​LindalyX-Lee @​Links2008 @​Linux2010 @​LinzeShi @​lisandromachado @​LiuwqGit @​liuyu1984 @​ljluestc @​lkanowski @​LLagoon3 @​llmsommelier @​loading2332 @​lonexreb @​lqsyyy @​lucthaobybgkw3232-eng @​ly85206559 @​m888m @​MagMueller @​maliv2 @​MarMarLabs @​Marvinthebored @​masatohoshino @​mattkanwisher @​maximilien @​maximilliangrand @​mcaxtr @​mcfex @​mezotv @​mgonto @​michaelrobertexp-source @​migelizaga-rgb @​mikasa0818 @​Mike-MWT @​mike-nott @​ml12580 @​mmhzlrj @​MoerAI @​MonkeyLeeT @​montrellcruse @​moonbow0407 @​mushuiyu886 @​mwbroxson @​n0mad-ai @​n572770 @​namest504 @​Navras98 @​NianJiuZst @​nierob-cmd @​nikolay-bratanov @​nikosml @​nina-grech @​njuboy11 @​nkeil @​nocodet888-arch @​noelillinger @​notlakshitha @​NOVA-Openclaw @​nv-kasikritc @​nxmxbbd @​obviyus @​oEdyb @​Oldrich333 @​Olli0103 @​ooiuuii @​oshaughnessy-junior @​OWWZO @​oywino @​papakpmartin @​Patrick-Erichsen @​PatrickTrent @​paulcam206 @​PaulClawitzki @​PaulD-LeWagon @​pbreault @​peach980 @​Peetiegonzalez @​personaltrainerkoichan @​petergaultney @​Phillis @​Piyushrathoree @​pkinjo @​pmochine @​PollyBot13 @​potoior @​potterdigital @​PratikRai0101 @​pstarkgit @​qingminglong @​quqi1599 @​qwexs @​qxr666-sga @​RaphazZze @​Raymondriter @​rboy1 @​rdbartram @​residentb2b @​resinoftree97 @​rh7 @​Ricardodpalmeida @​RileyJJY @​rjdotdev @​rmoskal @​Robbie-Microsoft @​Rocuts @​Roddmason @​rogerallen1 @​rogeriochaves @​RomneyDa @​rozenpl @​rsdancey @​rudycelekli @​ruel225 @​ruiling-smartbear @​ruirui666888 @​rvelasquez @​RXQ6 @​ryan-dyer-sp @​s3d1K0 @​SabaTech-dev @​sagebhardt @​salad-maker @​saladinyao-cyber @​sallyom @​SanderHelgesen @​sasan1200 @​SBC2016 @​SC-10749 @​sdamian @​SeanLiu326 @​SebTardif @​Sedrak-Hovhannisyan @​sercada @​serg0x @​service-cyber @​sesgoe @​Shagrat2 @​shakkernerd @​shannon0430 @​Shenrui-Ma @​shojikumaru @​Simon2256928 @​skyzhao1223 @​snotty @​sobolevbel @​Solvely-Colin @​stackingrockss @​steipete @​Stronggenetics @​sukhdeepjohar @​sunlit-deng @​SunnyShu0925 @​synthalorian @​syxscott @​szafranski @​Takhoffman @​technicalpickles @​TheAngryPit @​tianhaotian @​TommyLei666 @​TomSchuman @​tre1d @​TUARAN @​Twilight-Networks @​UlisesGascon @​umeranjum17 @​Uraroga @​usimic @​VACInc @​valkyriweb @​Veda-openclaw @​veritasaiflows-cell @​viernesmybot @​vildevev @​vincentkoc @​vinsew @​vishnusenthil-16 @​vishwanathmuthuraman @​vixenclawsastraagent @​vmbbz @​vobornik @​von8794 @​vyctorbrzezowski @​wangbaobisheng @​wangjx-xydt @​wangmiao0668000666 @​wangyan2026 @​warezio @​waynegault @​woohahahaaa @​wpu911 @​wr-web @​wtom @​wynxo @​xiajiahang @​xialonglee @​xiaopan-xydt @​xili-ytl @​xilopaint @​xpeng5278-web @​xx1170822819 @​xydigitLybnnnn @​xydt-juyaohui @​xyrolle @​YangManBOBO @​yashas-13 @​yasuhito @​yeager @​yetval @​Yigtwxx @​YiWang24 @​ylcn91 @​Yolo521-bot @​yousan @​yoyo837 @​yozakura-ava @​yozu @​ysumatta @​Yun-0000 @​YuriyPopovDev @​ywjanewer @​zabealbe @​zekth @​ZengWen-DT @​zhangguiping-xydt @​zhupeng0o0 @​zhuyankarl @​zori7 @​zrzavywa

Release verification

openclaw 2026.10.10-beta.5

2026.10.10-beta.5

Highlights

Changes

Fixes

  • Security boundaries: require approval for test/[ -v operands in exec allowlist mode, refuse browser proxy commands sent through generic node invoke, fail closed when sandboxed spawned children resolve CLI-backed models, carry workspaceOnly into Gateway-built delegate and media tools, keep unresolved Microsoft Teams allowlists restrictive, stop crafted Teams HTML from stalling the Gateway before sender checks, refuse embedded Control UI auth on pinned Android Gateway connections, and audit symlinked workspace skill roots. (#180880, #179880, #178742, #185094, #184989, #183438, #180843, #182384; related #111797) Thanks @​eleqtrizit, @​RomneyDa, @​LeizhenZhang, and @​dineshsuthar123.

... (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
  • 7dc3350 fix(process): share inherited process lineage across module copies
  • 81df37d test(update): give Doctor receipt retention a realistic deadline
  • 0c755e0 fix(claude-cli): keep the parent session when completions mediate file tools
  • 914d1ae fix(agents): keep the portal tool declared on non-owner turns
  • d75937c fix(agents): keep CLI completion tool catalogs stable (#176892)
  • 465b0b7 ci(release): reclaim hosted runner disk before Docker and live lanes
  • d562323 fix(file-transfer): share one workspace command import between memory and skills
  • 8c275c6 test(gateway): wait out Codex's unload confirmation window before physical exit
  • 216b1df fix(sqlite): wait for a cold database turn before the shared worker open queue
  • f6a0243 test(ui): match packaged Workboard mock Gateway to the served build
  • 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.10.10.
- [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.10.10)

---
updated-dependencies:
- dependency-name: "@openclaw/zalouser"
  dependency-version: 2026.10.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

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 6, 2026
@clawsweeper

clawsweeper Bot commented Nov 6, 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: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Nov 6, 2026
@clawsweeper

clawsweeper Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs real behavior proof before merge.

What this changes

Updates the Zalo Personal fixture fallback to @openclaw/zalouser 2026.10.10, including its lockfile and bundled TypeBox version.

Example: The configured Zalo Personal npm tag is unavailable.

  • Before: Crabpot materializes the pinned 2026.10.9 fallback.
  • After: Crabpot materializes the pinned 2026.10.10 fallback.

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) Useful fixture maintenance, but source attribution is incorrect and the changed credential and migration paths lack qualifying evidence.
Proof confidence 🧂 unranked krab (1/6) Real behavior proof is necessary before merge. See Before merge.
Patch quality 🦪 silver shellfish (2/6) Security review found an item that needs attention.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Crabpot's fallback fixture does not cover the newly published Zalo Personal package and its changed host contracts.
Reason: Maintaining representative published fallback fixtures has established merged precedent, and this artifact contains substantive contract changes beyond a version label.

Merge readiness

⛔ Blocked before merge - 7 items remain

Keep this PR open: main still pins 2026.10.9, and the update introduces incorrect source attribution that needs repair before merge.

Priority: P3
Reviewed head: 87bc97e987df17bf3011648a3bf83cd6a5aade52

Before merge

  • Add real behavior proof - Authority-chain proof required: exercise the selected artifact's real credential-store owner with a current login and a revoked or superseded login, demonstrating successful authorized persistence and rejection before unauthorized persistence. This bot PR is outside the ordinary contributor proof gate; its passing fixture check does not establish that authority scenario. Redact credentials and non-public endpoints. 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 both source references with the fallback pin (P2) - When the configured tag is unavailable, materialization selects 2026.10.10, whose registry record and archive contain no gitHead. readPackagePayloadSourceRef therefore sees a payload matching this new pin and packageEvidenceRef returns the unchanged manifest reference 8b18b5578f66eab1501cba4cef2310d88bfb9a41, attributing the new artifact to the preceding prepared source. Update crabpot.config.json's Zalo Personal source.ref and this shim's crabpot.sourceRef together using verified prepared-artifact provenance, and refresh affected generated expectations as required by AGENTS.md.
  • Resolve security concern: Establish revocation enforcement at credential persistence - The archive moves assertCurrent from individual credential operations into openKeyedStoreV2 construction and removes older-store paths; no concrete bypass was established, but supplied evidence does not demonstrate rejection of a revoked or superseded login before the store write.
  • Resolve merge risk - The PR owner must establish that a revoked or superseded Zalo login cannot persist credentials through the newly selected store API before adopting this fallback.
  • Improve patch quality - Prove a revoked or superseded login cannot persist credentials through openKeyedStoreV2, and verify existing credentials and legacy DM sessions survive the upgrade.
  • 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 package and prepared-source pairing - aa34909: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 deliberately paired the preceding npm fallback with verified prepared-source provenance while preserving moving tracks and the host.

Findings

  • [P2] Update both source references with the fallback pin — plugins/zalouser/package.json:7
  • [medium] Establish revocation enforcement at credential persistence — plugins/zalouser/package.json:7

Provenance

Tests

  • Missing end-to-end proof: Exact-fallback qualification does not show current versus revoked credential writes or an upgrade preserving existing credentials and legacy DM sessions.
Agent review details

How this fits together

Crabpot materializes configured plugin fixtures, inspects their contracts against an OpenClaw host, and produces compatibility 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]
Loading

Technical review

Best possible solution:

Pair the fallback with its verified prepared source in both existing references and qualify the changed credential and migration paths without changing moving tracks or the host pin.

Do we have a high-confidence way to reproduce the issue?

The attribution defect follows directly from the inspected archive lacking gitHead and the report owner selecting the unchanged source reference when its version matches the new pin; no target code was executed.

Is this the best way to solve the issue?

Updating the existing fallback is consistent with established maintenance, but the package pin alone is incomplete because attribution deliberately depends on its paired source reference.

Full review comments:

  • [P2] Update both source references with the fallback pin — plugins/zalouser/package.json:7
    When the configured tag is unavailable, materialization selects 2026.10.10, whose registry record and archive contain no gitHead. readPackagePayloadSourceRef therefore sees a payload matching this new pin and packageEvidenceRef returns the unchanged manifest reference 8b18b5578f66eab1501cba4cef2310d88bfb9a41, attributing the new artifact to the preceding prepared source. Update crabpot.config.json's Zalo Personal source.ref and this shim's crabpot.sourceRef together using verified prepared-artifact provenance, and refresh affected generated expectations as required by AGENTS.md.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.94

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 497e477988b6.

Merge-risk options

Maintainer options:

  1. Qualify credential authority before adoption (recommended)
    The PR owner supplies production-owner evidence that current login writes succeed and revoked or superseded login writes are rejected before persistence.
  2. Retain the reviewed fallback
    A maintainer defers this update and retains 2026.10.9 until the changed credential path is qualified.

Provenance checked

Testing

Proof path: in-process harness.

Security

Needs attention: Archive integrity and package identity match, but the changed credential-authority path needs final-write evidence.

Evidence

Security concerns:

  • [medium] Establish revocation enforcement at credential persistence — plugins/zalouser/package.json:7
    The archive moves assertCurrent from individual credential operations into openKeyedStoreV2 construction and removes older-store paths; no concrete bypass was established, but supplied evidence does not demonstrate rejection of a revoked or superseded login before the store write.
    Confidence: 0.9

What I checked:

  • Pinned change and current main: The introduced diff changes only the package and lockfile pins; main retains 2026.10.9, while both source references remain 8b18b5578f66eab1501cba4cef2310d88bfb9a41. (plugins/zalouser/package.json:7, 87bc97e987df)
  • Reachable source-attribution defect: readPackagePayloadSourceRef passes the actual payload version, updated shim pin, and unchanged manifest reference to packageEvidenceRef; matching versions without gitHead select that old reference. (scripts/report-lib.mjs:334, 497e477988b6)
  • Deliberate paired-pin contract: build(deps): refresh plugin pins and qualify compatibility evidence #401 introduced version-qualified attribution; chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 paired the preceding fallback refresh with its prepared source and distinguished exact fallback qualification from moving-track CI. (scripts/report-provenance.mjs:3, 384001272947)
  • Published dependency identity and policy boundary: Read both registry records and npm archives without execution; SHA-512 values match the locks, neither supplies gitHead, and neither declares lifecycle scripts. The new archive changes credential persistence, setup policy handling, and Doctor session migration. Crabpot materializes and executes this dependency in fixture qualification, establishing the dependency-contract boundary; its complete root and extensions policies were read at the publication revision. (extensions/AGENTS.md, 669193e3c42e)
  • Credential authority and persisted-state changes: The published archive switches credential writes to openKeyedStoreV2 with assertCurrent supplied at store creation, removes older-store fallbacks, and changes Doctor's legacy session reads to asynchronous owner APIs. Its npm attestation identifies publication run https://github.com/openclaw/openclaw/actions/runs/41561283760; the artifact index names prepared source 7dc3350cb9f08fcf9a0af5c4845a20d5b2f1a8be. Qualification artifact contents could not be inspected because their Azure download host is blocked; that limitation is not a contributor defect. (extensions/zalouser/src/session-state.ts, 669193e3c42e)
  • Discussion, checks, and canonical search: The complete substantive body and both comments contain no changed-path runtime or upgrade evidence; comments are automated acknowledgments. The isolated Zalo Personal fixture and lock-security checks passed, while other Default Track checks remained in progress. Searches found no merged or open replacement owning the 2026.10.10 update. (87bc97e987df)

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)

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.

Labels

Label changes:

  • add P3: Routine fixture maintenance with a bounded source-attribution defect and no demonstrated urgent user regression.
  • add merge-risk: 🚨 security-boundary: The selected artifact changes how current-login authority guards persisted credentials; successful static fixture qualification does not establish rejection after revocation.
  • add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦪 silver shellfish.
  • 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 source-attribution defect and no demonstrated urgent user regression.
  • merge-risk: 🚨 security-boundary: The selected artifact changes how current-login authority guards persisted credentials; successful static fixture qualification does not establish rejection after revocation.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🦪 silver shellfish.
  • status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

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

@dependabot @github

dependabot Bot commented on behalf of github Nov 8, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #767.

@dependabot dependabot Bot closed this Nov 8, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/zalouser/openclaw/zalouser-2026.10.10 branch November 8, 2026 09:14
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: 🚨 security-boundary 🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data. 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: 📣 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.

0 participants