Skip to content

chore(deps): bump @openclaw/google-meet from 2026.10.9 to 2026.11.3 in /plugins/google-meet - #832

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps @openclaw/google-meet from 2026.10.9 to 2026.11.3.

Release notes

Sourced from @​openclaw/google-meet'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/google-meet'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/google-meet](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/google-meet"
  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 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 14, 2026
@clawsweeper

clawsweeper Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge.

What this changes

Updates the Google Meet fixture’s fallback package and lockfile from 2026.10.9 to 2026.11.3.

Example: The configured Google Meet npm tag is unavailable.

  • Before: Crabpot falls back to @openclaw/google-meet@2026.10.9.
  • After: Crabpot falls back to @openclaw/google-meet@2026.11.3.

Review scores

Measure Result What it means
Overall readiness 🦪 silver shellfish (2/6) The package and lock agree, but source attribution is incorrect and the recorded qualification prerequisite remains unmet.
Proof confidence 🌊 off-meta tidepool Not applicable: This Dependabot-authored fixture update is outside the ordinary contributor proof gate; archive verification establishes package identity, while supplied CI does not qualify the exact fallback through native host admission.
Patch quality 🦪 silver shellfish (2/6) 1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: No · Fix scope: Complete
User problem: Crabpot’s pinned Google Meet fallback trails the newer published package.
Reason: Recorded maintainer direction defers these updates until the separately owned qualification prerequisite is complete; this PR does not establish that prerequisite or a reason to override it.

Merge readiness

⛔ Blocked before merge - 4 items remain

Main still pins 2026.10.9, so the permitted close condition is unmet; this PR also introduces incorrect source attribution and precedes the recorded host-qualification prerequisite.

Priority: P2
Reviewed head: 1befd06f028028c4a8df20a498db7400e36ad5af

Before merge

  • Update both source references with the fallback version (P2) - When tag resolution falls back to 2026.11.3, neither the registry metadata nor package.json supplies gitHead. readPackagePayloadSourceRef therefore matches the payload against this changed shim version and selects crabpot.config.json’s retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, documented as prepared source for 2026.10.9. Reports consequently link the new artifact to the old source revision. Verify the publication’s prepared source and update both the manifest reference and this shim’s sourceRef together.
  • Resolve merge risk - Maintainers must complete the eligible-host qualification and promotion tracked in Qualify a newer Default Track host before refreshing official plugin fallbacks #780 before landing this newer fallback: the current 2026.10.6 host cannot natively admit its >=2026.11.3 plugin API requirement.
  • Product: not worth merging - Recorded maintainer direction defers these updates until the separately owned qualification prerequisite is complete; this PR does not establish that prerequisite or a reason to override it.
  • Explain or restore the original intent of Fallback package and source pairing - aa34909: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 updated fallback packages together with their verified prepared-source references while preserving independent host qualification.

Findings

  • [P2] Update both source references with the fallback version — plugins/google-meet/package.json:7

Provenance

Tests

  • Missing end-to-end proof: The supplied checks do not establish native admission and execution of the exact 2026.11.3 fallback on a qualified eligible host.
Agent review details

How this fits together

Crabpot resolves fixture packages, inspects their plugin contracts against an OpenClaw host, and produces compatibility reports with upstream source links.

flowchart TD
  A[Fixture manifest] --> B[Package tag resolution]
  B --> C[Published package]
  B --> D[Pinned fallback shim]
  D --> C
  C --> E[Compatibility inspection]
  E --> F[Reports and source links]
Loading

Technical review

Best possible solution:

Retain the reviewed fallback until host qualification is complete, then refresh the exact package with publication-verified source references and matching report expectations.

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

Source and integrity-verified archive metadata establish that the 2026.11.3 fallback without gitHead receives the retained 2026.10.9 source reference; no target code or tests were executed.

Is this the best way to solve the issue?

The existing package-and-lock mechanism is appropriate, but this update needs matching publication-source references and must follow the recorded host-qualification sequence.

Full review comments:

  • [P2] Update both source references with the fallback version — plugins/google-meet/package.json:7
    When tag resolution falls back to 2026.11.3, neither the registry metadata nor package.json supplies gitHead. readPackagePayloadSourceRef therefore matches the payload against this changed shim version and selects crabpot.config.json’s retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, documented as prepared source for 2026.10.9. Reports consequently link the new artifact to the old source revision. Verify the publication’s prepared source and update both the manifest reference and this shim’s sourceRef together.
    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 90b39250dd03.

Merge-risk options

Maintainer options:

  1. Hold for host qualification (recommended)
    Maintainers retain the reviewed fallback while the separately tracked host prerequisite is completed.
  2. Complete qualification before landing
    Maintainers qualify and promote an eligible immutable host separately, then qualify the exact fallback package and source pair.

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

  • Exact introduced change: The pinned diff updates the package and lockfile to 2026.11.3 but leaves sourceRef at 8b18b5578f66eab1501cba4cef2310d88bfb9a41; GitHub confirms main remains 90b3925, where the fallback is 2026.10.9. (plugins/google-meet/package.json:7, 1befd06f0280)
  • Incorrect attribution path: readPackagePayloadSourceRef supplies the shim version and manifest source reference to packageEvidenceRef; without gitHead, a matching payload version selects that retained reference. (scripts/report-lib.mjs:330, 90b39250dd03)
  • Publication pairing contract: Operations guidance requires matching manifest and shim source references, identifies the retained SHA as prepared source for 2026.10.9, and requires publication qualification when gitHead is absent. (docs/operations.md:50, 90b39250dd03)
  • Original pairing intent: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 deliberately refreshed fallback versions with verified prepared-source references while retaining the independently qualified host. (plugins/google-meet/package.json:15, aa349094d146)
  • Published package metadata: Read-only, in-memory archive inspection verified both versions against registry SHA-512 integrity values. Neither registry nor package metadata supplies gitHead or package lifecycle scripts. The 2026.11.3 archive declares plugin API >=2026.11.3 and TypeBox 1.3.35; its registry integrity matches the changed lockfile.
  • Authoritative host admission: Crabpot’s pinned host reports version 2026.10.6; its native discovery skips non-bundled packages whose plugin API range excludes that host. This runtime contract is relevant because Crabpot executes these fixtures against that host. (src/plugins/discovery-availability.ts:26, 5f84c5b8a988)

Likely related people:

  • Peter Steinberger: Raw commit aa34909 adds plugins/google-meet/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/google-meet/package.json)
  • Vincent Koc: Raw commit 614b320 adds plugins/google-meet/package.json:5 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/google-meet/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 affects fixture provenance and compatibility qualification, with no demonstrated urgent deployed-user outage.
  • add merge-risk: 🚨 compatibility: The fallback raises its native plugin API floor to >=2026.11.3 while the qualified host remains 2026.10.6; the recorded host prerequisite remains unresolved.
  • add rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🌊 off-meta tidepool 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 affects fixture provenance and compatibility qualification, with no demonstrated urgent deployed-user outage.
  • merge-risk: 🚨 compatibility: The fallback raises its native plugin API floor to >=2026.11.3 while the qualified host remains 2026.10.6; the recorded host prerequisite remains unresolved.
  • rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🌊 off-meta tidepool 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:37 AM ET / 09:37 UTC.

@dependabot @github

dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #860.

@dependabot dependabot Bot closed this Nov 19, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/google-meet/openclaw/google-meet-2026.11.3 branch November 19, 2026 09:25
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