Skip to content

chore(deps): bump @openclaw/discord from 2026.7.1 to 2026.9.6 in /plugins/discord - #379

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

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

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 27, 2026

Copy link
Copy Markdown
Contributor

Bumps @openclaw/discord from 2026.7.1 to 2026.9.6.

Release notes

Sourced from @​openclaw/discord's releases.

openclaw 2026.9.6

macOS app rebuilt 2026-09-24: the original 2026.9.6 macOS build crashed at launch (#156861) and was replaced at 09:52 UTC by a rebuilt, notarized 2026.9.6 build with the fix (#156881). Download the DMG below or update from 2026.9.5 in the app. If you installed the earlier 2026.9.6 build and it does not launch, install the DMG once. The npm package is unchanged.

OpenClaw v2026.9.6

178 direct commits · 2,614 pull requests · 351 contributors

Changes included in this release

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

  • Release notes — formatted for people, with expandable sections.
  • Changelog — plain Markdown for AI agents and tools.

Thanks

@​0-danielviktorovich-0 @​1Vision365-PeterTijsma @​609NFT @​aatreya @​abacha @​AbuSido82 @​agebreak0083 @​agent-axos @​AgentSolomon @​ago1776 @​Albertyn87 @​alex-brave @​alexey-pelykh @​Alix-007 @​allen0373 @​altaywtf @​alvelda @​amittell @​Andapeng @​aniketkrs @​aniruddhaadak80 @​anyech @​ayoakouh @​azuretek @​baiwei0427 @​baovo15 @​Bartok9 @​Baumus @​bdjben @​beeven @​beings1988-lab @​bek91 @​benediktweber @​berklingtools @​bharatvasan @​BinChenUtrecht @​bipolar84 @​bitbalancer @​blackeyes-boy @​bobbygaerd @​BodegaClaw @​BorClaw @​BottaniCals @​britrik @​brokemac79 @​Bruce-Yii @​brunorapido @​BsnizND @​camerono @​Carme99 @​ceckert @​CHE10X @​chelsealong @​cipp-ashe @​cjn119-ui @​ckupferschmid @​cloudgg82-blip @​cnflwzh @​cognos2013 @​colehammond65 @​Colton-Harris @​ComfyChloe @​Conan-Scott @​cookywook @​cortanapham @​cpsleepy @​ctbritt @​Cyb3rb1ade @​dale-goes-fast @​damiansmazurek @​dankarization @​DasX @​davidchyi-beep @​davidcittadini @​Davidofflol12 @​Dazlarus @​ddupg @​Deregtx @​desksk @​destinedenergy @​dh-js @​dimonnld @​dltlaos11 @​dmlau76 @​dmnksss @​dom521 @​DonnieFi @​droidyouwerelookingfor @​DrToNy1 @​dustytext-bot @​duybaovin @​easyteacher @​edenfunf @​edgarstool @​edrwalker @​eefreenyc @​Eragim @​ericcaiwx-star @​ericcurtin @​ericpearson @​ERMALTA @​etzelm @​ezimerman @​Fatal0607 @​fduch-stranger @​fede-kamel @​flynnmcpoc @​flyto168 @​fozzels-assistant @​fray-ai @​freshxiaoyao @​fulgerulnegru @​fuller-stack-dev @​Gabrielnkl @​galiniliev @​ge0el @​gennadyclaw @​giodl73-repo @​GoldenrodScript @​gorkem2020 @​goutamadwant @​Grynn @​guarismo @​guerilla47 @​gwjr @​Haderach-Ram @​hannesrudolph @​hannnnn-l @​harjothkhara @​harshitgupta31415 @​hartmark @​HaukeSchnau @​hhkwoong @​holny @​hpyhandsome @​hxy8241 @​hxy91819 @​HypocritePro @​imHw @​isinghmitesh @​islandpreneur007 @​itanyplus @​iuiu-py @​ivankuznetsov @​IWhatsskill @​iXandru @​Jackten @​jacobtomlinson @​jalehman @​jammyclaw @​jarvis-stephens-bot @​jason-allen-oneal @​jaxonparrott @​jb510 @​jesse-merhi @​Jey2311 @​jhgaylor @​jiangwanxin1982-ctrl @​jjgao @​jjjhenriksen @​jnikolaidis @​johnnyjrizzo @​joncursi @​JoPaMu @​joshavant @​joshpetras @​jplavoiemtl @​jzakirov @​KarleeTDM @​keithce @​kevinlin-openai @​Kiiatkin @​Kimiyu-186 @​kip-claw @​kiranvk-2011 @​kittitys @​kpwillis @​KrasimirKralev @​KrauseFx @​KrisWuli006 @​L497c @​lakemike @​LandonSchropp @​laurencebrown @​laurenceputra @​Lendersmark @​Leon-SK668 @​Lidashi1025 @​lishewen @​LiuwqGit @​lojasarah @​lraesly @​lucarinaorg @​ludovicfourrage @​ly85206559 @​marcio-absmartly @​markGenhealth @​markun-japan @​Marvinthebored @​masatohoshino @​massad1977 @​MasterSwords1 @​mattkanwisher @​maxsxu @​Maxwell-Code07 @​mcaxtr @​MertBasar0 @​metahacker @​mfurkanakinci @​michaeljgood71 @​migelizaga-rgb @​milanko77 @​miorbnli @​mirasrael @​Mirr0ch1 @​mmkerrigan @​mmm7053455-tech @​MoerAI @​mrunalp @​mrzeepek @​msobrosa @​mulderp82 @​mykhul @​najef1979-code @​Navras98 @​ndakota79 @​neangneatos @​Nehanth @​NianJiuZst @​Nickfost @​nikolasdehor @​noelillinger @​Nsikak1 @​Ntimesp @​nxmxbbd @​obviyus @​Oldrich333 @​omarshahine @​ooiuuii @​original4422 @​oshunter @​ozp @​paluj85-cloud @​pash-openai @​Patrick-Erichsen @​Peetiegonzalez @​PennyVibe @​petroff @​pfrederiksen @​Philbones49 @​piotx @​podulator @​PollyBot13 @​Psychnix @​qingminglong @​qq1091429090huo-svg @​raghidtawil-lab @​rajivranjanmars @​RichSomeday222 @​RJAILLC @​rlosito @​rmyers64 @​RomneyDa @​rondavis007 @​ruel225 @​rvelasquez @​RWOverdijk @​saariuslystoned @​sac916 @​safrano9999 @​sagebhardt @​sahilsatralkar @​sallyom @​samiralibabic @​sasan1200 @​SBC2016 @​seahopark @​sebastian-hoebarth @​sennyhoney @​sercada @​servermacminim2ku @​shadesurgeon @​shakkernerd @​sjf @​sjf-oa @​skorfmann @​sloptop-the-terrible @​smaill02 @​smfworks @​soar-king @​Solvely-Colin @​SPRIC76 @​stackingrockss @​steipete @​stevekinney @​stevenlee-oai @​StrajnarFilip @​Suidge @​SummitOperations26 @​SunnyShu0925 @​synapse-homeroot @​synthalorian @​Takhoffman @​Tangqiu25 @​th-m-vogel @​TheAngryPit @​todddickerson @​tomekep @​TommyLei666 @​TriDefender @​Truck0ff @​tzy-17 @​VACInc @​Valkster70 @​Vasanthdev2004 @​VictoryLapOps @​vildar82 @​vincentkoc @​voytas75 @​vyctorbrzezowski @​wangmiao0668000666 @​wangzhongming-yh @​WhitenessTiger @​wiipud @​Wildsberg @​wlassalle724 @​wrgrant @​xialonglee @​xilopaint @​xingzihai @​xydigit-zt @​xydigitLybnnnn @​xydt-juyaohui @​Yachiyo1680 @​YangManBOBO @​yetval @​Yigtwxx @​Yun-0000 @​yunligou711-commits @​yursil @​ZaneChen76 @​ZaneMc-AO @​ZengWen-DT @​zesming @​zhangguiping-xydt @​zl0nline @​zsh20000414 @​ZSmallX @​ZYV5ge @​zyz619963502zyz @​zzs12345-web

  • ayoakouh
  • Benjamin Badejo
  • CanadaOrNaw
  • Claw
  • Galin Iliev
  • Mariano
  • Peter Steinberger
  • Peter Steinberger
  • Pinchy
  • Prince
  • root
  • svenmy76
  • thomas.szbay
  • Vyctor
  • wangzifei
  • Yuri Petrou

Release verification

... (truncated)

Changelog

Sourced from @​openclaw/discord'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
  • eb377ac chore(release): regenerate the 2026.9.6 contribution record for the predecess...
  • 1d8c0fc fix(update): stop a replaced-installation Gateway without draining it and bou...
  • ee8f55c fix(daemon): keep the spy-able ownership assertion in systemd start and admit...
  • 55700ea chore(update): parse the recorded predecessor-stop identity without a type as...
  • 6eed4c6 chore(release): regenerate the 2026.9.6 contribution record for the predecess...
  • 80b922d fix(update): record the predecessor stop at its mutation boundary, restore it...
  • d1531b5 chore(release): regenerate the 2026.9.6 contribution record for the cut-5 fixes
  • 57c179a chore(update): keep the predecessor-stop ledger step constant module-private
  • 523cd02 fix(update): stop the supervised predecessor Gateway in the delegated Doctor ...
  • 945557e fix(daemon): let a loaded user unit vouch for itself when system ownership is...
  • 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/discord](https://github.com/openclaw/openclaw) from 2026.7.1 to 2026.9.6.
- [Release notes](https://github.com/openclaw/openclaw/releases)
- [Changelog](https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md)
- [Commits](openclaw/openclaw@v2026.7.1...v2026.9.6)

---
updated-dependencies:
- dependency-name: "@openclaw/discord"
  dependency-version: 2026.9.6
  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 Sep 27, 2026
@clawsweeper

clawsweeper Bot commented Sep 27, 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 P2 Normal priority bug or improvement with limited blast radius. merge-risk: 🚨 automation 🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Sep 27, 2026
@clawsweeper

clawsweeper Bot commented Sep 27, 2026

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge. Reviewed September 27, 2026, 5:11 AM ET / 09:11 UTC.

ClawSweeper review

What this changes

Updates Crabpot’s Discord plugin fixture dependency and lockfile from @openclaw/discord 2026.7.1 to 2026.9.6.

Merge readiness

⛔ Blocked before merge - 3 items remain

The fallback Discord package pin is still 2026.7.1 on current main, so this PR remains useful. The corresponding source reference needs to advance before the fixture’s package and source records are aligned.

Priority: P2
Reviewed head: 2f3b4b55cc7f130c66d4c5ca19a7ae0985d94cba

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) The pin and lockfile are coherent, but the source reference needs alignment before the fixture record is complete.
Proof confidence 🌊 off-meta tidepool Not applicable: This bot-authored fixture-pin PR is exempt from contributor runtime proof. The changed production input is the Discord npm artifact; the repository’s source/package smoke and fixture checks remain the relevant validation, and no stored-data contract changes.
Patch quality 🦐 gold shrimp (3/6) 1 actionable review finding remain.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: This bot-authored fixture-pin PR is exempt from contributor runtime proof. The changed production input is the Discord npm artifact; the repository’s source/package smoke and fixture checks remain the relevant validation, and no stored-data contract changes.
Evidence reviewed 6 items Introduced package update: The PR changes the Discord fixture dependency to 2026.9.6 and updates its lockfile.
Current-main need: Current main still pins the fallback Discord dependency to 2026.7.1, while the default track and generated report already use 2026.9.6.
Source reference: The Discord fixture source reference remains at a July revision whose upstream package version is 2026.7.1.
Findings 1 actionable finding [P2] Advance the Discord source reference with the package pin
Security None None.

How this fits together

Crabpot inspects an OpenClaw Discord plugin fixture using npm package and source records. Its checks and generated reports describe the plugin’s compatibility with the pinned OpenClaw host.

flowchart LR
  A[Discord package pin] --> B[Fixture materialization]
  C[OpenClaw source reference] --> B
  B --> D[Compatibility checks]
  D --> E[Generated reports]
Loading

Before merge

  • Advance the Discord source reference with the package pin (P2) - The new fallback pin is 2026.9.6, but crabpot.config.json still points the Discord source record at a revision declaring 2026.7.1. Update that reference and refresh affected expectations so source-linked fixture evidence identifies the package version being reviewed.
  • Resolve merge risk (P2) - The fallback package pin would identify Discord 2026.9.6 while its configured source reference still identifies 2026.7.1; source-linked compatibility evidence may then describe the wrong version.
  • Complete next step (P2) - Align the Discord source reference with the 2026.9.6 package and verify source-mode and package-mode fixture output before merge.

Findings

  • [P2] Advance the Discord source reference with the package pin — plugins/discord/package.json:7
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Dependency update 2 files changed; lockfile +674/-85 lines The lockfile records a substantially expanded bundled dependency graph for the new package.

Merge-risk options

Maintainer options:

  1. Align the fixture source (recommended)
    Advance the Discord source reference to the 2026.9.6 release and check the resulting source and package reports.
Copy recommended automerge instruction
@clawsweeper automerge

Special instructions:
Align the Discord source reference in crabpot.config.json with the OpenClaw 2026.9.6 release, refresh affected generated expectations, and validate source-mode and package-mode fixture inspection.

Technical review

Best possible solution:

Keep the exact 2026.9.6 package pin and align the Discord source reference with that release, then verify the source and package inspection outputs.

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

Not applicable: this PR refreshes a fixture dependency rather than reporting a runtime bug. The source/package version mismatch is visible in the checked-in records.

Is this the best way to solve the issue?

Yes, updating the exact package pin is the appropriate fixture change; the matching source reference should advance with it.

Full review comments:

  • [P2] Advance the Discord source reference with the package pin — plugins/discord/package.json:7
    The new fallback pin is 2026.9.6, but crabpot.config.json still points the Discord source record at a revision declaring 2026.7.1. Update that reference and refresh affected expectations so source-linked fixture evidence identifies the package version being reviewed.
    Confidence: 0.88

Overall correctness: patch is incorrect
Overall confidence: 0.86

AGENTS.md: found and applied where relevant.

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

Labels

Label changes:

  • add P2: This is a bounded fixture refresh with a source/package provenance mismatch to resolve.
  • add merge-risk: 🚨 automation: Fixture reports can retain an older source reference after the package pin advances because the report-refresh workflow does not change fixture configuration.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This bot-authored fixture-pin PR is exempt from contributor runtime proof. The changed production input is the Discord npm artifact; the repository’s source/package smoke and fixture checks remain the relevant validation, and no stored-data contract changes.

Label justifications:

  • P2: This is a bounded fixture refresh with a source/package provenance mismatch to resolve.
  • merge-risk: 🚨 automation: Fixture reports can retain an older source reference after the package pin advances because the report-refresh workflow does not change fixture configuration.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This bot-authored fixture-pin PR is exempt from contributor runtime proof. The changed production input is the Discord npm artifact; the repository’s source/package smoke and fixture checks remain the relevant validation, and no stored-data contract changes.

Evidence

Acceptance criteria:

  • [P1] CRABPOT_PLUGIN_INSPECTOR_CLI=source npm run plugin-inspector:smoke.
  • [P1] npm run plugin-inspector:smoke.
  • [P1] node scripts/inspect-fixtures.mjs --check.

What I checked:

Likely related people:

  • Peter Steinberger: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
  • Vincent Koc: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rank-up moves

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

  • Update the Discord source reference and verify the source and package inspection outputs.

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@dependabot @github

dependabot Bot commented on behalf of github Oct 3, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #408.

@dependabot dependabot Bot closed this Oct 3, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/discord/openclaw/discord-2026.9.6 branch October 3, 2026 09:05
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: 🚨 automation 🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation. P2 Normal priority bug or improvement with limited blast radius. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. 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