Skip to content

chore(deps): bump @openclaw/lobster from 2026.10.9 to 2026.11.4 in /plugins/lobster - #843

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps @openclaw/lobster from 2026.10.9 to 2026.11.4.

Release notes

Sourced from @​openclaw/lobster's releases.

openclaw 2026.11.4

OpenClaw v2026.11.4

220 commits · 125 pull requests · 90 contributors

Changes included in this release

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

Thanks

@​1052326311 @​abacha @​akang1798 @​alfred429 @​alkor2000 @​AlyaKoni @​amittell @​arpe1618 @​ausvald @​ava-perry @​Borekobama @​ceo633 @​daniel-lxs @​dankarization @​dlmccoy @​dmsrg399 @​DonnieFi @​eleqtrizit @​ensignwesley @​ericcaiwx-star @​erik-toc @​forrystudio @​fuller-stack-dev @​galiniliev @​garrytan @​goslingmanagment @​gulagala001 @​harjothkhara @​HermanZeng @​holgergruenhagen @​jalehman @​jason-allen-oneal @​Jo2234 @​jondihaynes @​JoPaMu @​joshavant @​kaguranananana @​KenAng-tech @​kir1ll @​kkernan @​LeizhenZhang @​Leon-SK668 @​lester076 @​lifuyue @​LiuwqGit @​masatohoshino @​mcaxtr @​McgAtom @​MertBasar0 @​mmaps @​momothemage @​mulderp82 @​najef1979-code @​obviyus @​ooiuuii @​oxen-horse @​patosullivan @​Patrick-Erichsen @​pgondhi987 @​piccolllo-vc @​ptu-gh @​rabsef-bicrym @​reisball @​rodricksz4h5 @​RomneyDa @​sallyom @​Satoshi-Kusumoto @​shakkernerd @​slange-a11y @​sopa-gpters @​steipete @​Stronggenetics @​syxscott @​thefourcraft @​tomdailey55 @​tommyjoseph @​tssala23 @​vincentkoc @​vyctorbrzezowski @​wangmiao0668000666 @​wr-web @​wupingyuan81-oss @​xRyann2255 @​Yachiyo1680 @​yetval @​yixiaoer-520 @​ylcn91 @​Yun-0000 @​yyds-xxxx @​zhangguiping-xydt

Release verification

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.

... (truncated)

Changelog

Sourced from @​openclaw/lobster'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
  • d843d6a fix(release): retry freshly uploaded artifact visibility
  • 62d12df fix(ci): align release plan cache runner routing
  • e283dcc test: isolate stateful e2e mock helpers and retain failure diagnostics
  • 83e8905 test: retain replay restart failure diagnostics
  • ab4f89a test: stabilize release validation fixtures
  • 88922ef test(ci): check release timing walls per packed stripe
  • 5800284 fix: resolve release validation regressions
  • a9b9fed fix(browser): correct document policy return contracts
  • ef63ed8 fix(browser): preserve request policy errors during navigation
  • 069f109 fix(ui): backport closing overlay fallback repair (#198658)
  • 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/lobster](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.4.
- [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.4)

---
updated-dependencies:
- dependency-name: "@openclaw/lobster"
  dependency-version: 2026.11.4
  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 19, 2026
@clawsweeper

clawsweeper Bot commented Nov 19, 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: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Nov 19, 2026
@clawsweeper

clawsweeper Bot commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge.

What this changes

This PR updates the Lobster fixture fallback to 2026.11.4 and its bundled TypeBox dependency to 1.3.35.

Example: Lobster’s latest tag is unavailable and Crabpot selects the pinned fallback.

  • Before: Crabpot selects @openclaw/lobster 2026.10.9.
  • After: Crabpot selects @openclaw/lobster 2026.11.4.

Review scores

Measure Result What it means
Overall readiness 🦪 silver shellfish (2/6) Artifact identity is verified, but the incomplete provenance update blocks the patch and host qualification remains deferred.
Proof confidence 🦐 gold shrimp (3/6) This bot-authored fixture maintenance update is outside the contributor demonstration gate; archive inspection establishes identity and metadata, while CI does not establish exact-fallback runtime qualification.
Patch quality 🦪 silver shellfish (2/6) 1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The frozen Lobster fallback trails the published package’s workspace-access declaration and bundled schema dependency.
Reason: Tracking official plugin contracts fits Crabpot’s fixture purpose, with owner direction already establishing the prerequisite qualification sequence.

Merge readiness

⛔ Blocked before merge - 3 items remain

Current main still pins Lobster 2026.10.9, so this PR is not implemented; incorrect source attribution and the recorded host-qualification prerequisite block landing.

Priority: P2
Reviewed head: ea58cf0ddc4d13203691f9ac10460f8744a212b9

Before merge

  • Pair the new fallback with its verified publication source (P2) - The 2026.11.4 registry metadata and archive omit gitHead, but the shim sourceRef and manifest source.ref still identify 8b18b5578f66eab1501cba4cef2310d88bfb9a41, explicitly paired with 2026.10.9. When the new fallback is materialized, scripts/report-lib.mjs passes matching artifact and shim versions to packageEvidenceRef, which consequently links the changed runtime implementation to that old source commit. Verify the prepared publication source, update both existing references, and regenerate the affected reports.
  • Resolve merge risk - Before merging, the host-qualification owners must complete the separately reviewed eligible-host promotion tracked in Qualify a newer Default Track host before refreshing official plugin fallbacks #780; the current 2026.10.6 host skips this package’s >=2026.11.4 plugin API contract.
  • Explain or restore the original intent of Lobster fallback and publication-source pairing - aa34909: Merged chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 paired exact fallback artifacts with verified prepared-source references while preserving the separately qualified host.

Findings

  • [P2] Pair the new fallback with its verified publication source — plugins/lobster/package.json:7

Provenance

Agent review details

How this fits together

Crabpot resolves plugin fixtures from package selectors or pinned fallbacks, inspects their contracts against a qualified OpenClaw host, and generates compatibility reports with source links.

flowchart LR
  A[Fixture manifest] --> B[Package selection]
  C[Pinned fallback] --> B
  B --> D[Lobster artifact]
  D --> E[Host contract inspection]
  E --> F[Compatibility reports]
Loading

Technical review

Best possible solution:

After the separately qualified host promotion, refresh the exact Lobster artifact together with its verified publication-source references and affected reports.

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

Source establishes that materializing 2026.11.4 without gitHead causes report links to select the retained 2026.10.9 source reference; no target code was executed.

Is this the best way to solve the issue?

The package and lockfile agree with the integrity-verified archive, but a complete fixture refresh must also update the existing source-pairing metadata and follow the recorded host-qualification sequence.

Full review comments:

  • [P2] Pair the new fallback with its verified publication source — plugins/lobster/package.json:7
    The 2026.11.4 registry metadata and archive omit gitHead, but the shim sourceRef and manifest source.ref still identify 8b18b5578f66eab1501cba4cef2310d88bfb9a41, explicitly paired with 2026.10.9. When the new fallback is materialized, scripts/report-lib.mjs passes matching artifact and shim versions to packageEvidenceRef, which consequently links the changed runtime implementation to that old source commit. Verify the prepared publication source, update both existing references, and regenerate the affected reports.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.99

AGENTS.md: found and applied where relevant.

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

Merge-risk options

Maintainer options:

  1. Wait for the qualified host (recommended)
    Keep this update pending the separately owned host promotion, then qualify the exact artifact and source pair under the recorded cohort-refresh plan.

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

Likely related people:

  • Peter Steinberger: Raw commit aa34909 adds plugins/lobster/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/lobster/package.json)
  • Vincent Koc: Raw commit 614b320 adds plugins/lobster/package.json:2 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/lobster/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 P2: This is a routine fixture refresh with a concrete report-provenance defect and no demonstrated urgent user regression.
  • add merge-risk: 🚨 compatibility: The exact package requires a plugin API newer than the qualified host, and an owner explicitly deferred this update series until host promotion.
  • add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦐 gold shrimp 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:

  • P2: This is a routine fixture refresh with a concrete report-provenance defect and no demonstrated urgent user regression.
  • merge-risk: 🚨 compatibility: The exact package requires a plugin API newer than the qualified host, and an owner explicitly deferred this update series until host promotion.
  • rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦐 gold shrimp 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 19, 2026, 4:26 AM ET / 09:26 UTC.

@dependabot @github

dependabot Bot commented on behalf of github Nov 20, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #864.

@dependabot dependabot Bot closed this Nov 20, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/lobster/openclaw/lobster-2026.11.4 branch November 20, 2026 09:12
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. P2 Normal priority bug or improvement with limited blast radius. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. 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