Skip to content

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

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

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

Release notes

Sourced from @​openclaw/google-meet's releases.

openclaw 2026.11.1

2026.11.1

Highlights

Changes

  • Claude CLI: saved subscription accounts can make configured models available without a separate native login, and operators can opt into native Agent and Workflow orchestration through plugins.entries.anthropic.config.managedNativeTools; the default remains off and restricted runs keep their existing tool limits. (#179203, #183765) Thanks @​RomneyDa.
  • Anthropic: API-key setup can record an optional Anthropic workspace ID; existing workspace headers are preserved, and workspace-scoped keys need no extra setting. (#186976) Thanks Ayaan Zaidi, @​evomach, @​sukhdeepjohar, @​RomneyDa.
  • Google: Interactions requests honor managed proxy and TLS settings, rotate eligible API keys before streaming after a rate limit, preserve native video input, and forward nucleus sampling consistently; choose google-generative-ai when explicit Gemini cache handles are required. (#189395, #190695) Thanks @​RomneyDa.
  • Bedrock Mantle: discovered numbered OpenAI GPT models select the Responses route automatically, while GPT-OSS keeps Chat Completions and Claude keeps Anthropic Messages. Thanks @​MertBasar0, @​anmol0b, @​shakkernerd, @​kybrcore, @​sukhdeepjohar, @​potoior, @​RomneyDa.
  • Control UI: the model picker shows the configured active context budget rather than only the model maximum, and short session links retain their intended navigation target. (#180870, #183148) Thanks @​RomneyDa.
  • Google Chat: remote HTTP(S) attachments are delivered as visible links alongside captions; local files and native uploads remain unsupported with service-account authentication. Thanks @​RomneyDa.
  • Update diagnostics: detailed readiness separates a ready core from channel outages, allowing repaired updaters to finish with named channel warnings without hiding HTTP 503 or weakening normal service-start checks. Thanks @​duyufansh2008, @​RomneyDa.

Fixes

  • Network and tool safety: ClickClack and ClawHub reject redirects into unrelated private services, Discord CDN downloads no longer inherit browser private-network access, and FIFO native-hook credentials are rejected without hanging the agent. (#190944, #190939, #191458, #191423) Thanks @​pgondhi987, @​SebTardif, and @​Leon-SK668.
  • Doctor consent and access policy: noninteractive checks no longer download plugins without repair consent, and explicitly empty group allowlists remain empty instead of being repopulated. (#191523, #174787) Fixes #191420, #173826 Thanks @​brandonulrich, @​steipete, and @​lockhartheavyindustries.
  • Recovery data: malformed UTF-8 legacy imports are rejected instead of replacing original content; failed skill restore rollbacks preserve the original copy, and cleanup refuses destructive work when workspace inspection fails. (#180861, #173954, #174195, #176362) Fixes #180782, #180795 Thanks @​RomneyDa, @​duyufansh2008, @​steipete, and @​wangmiao0668000666.
  • Log redaction: malformed custom entries no longer disable valid rules or built-in secret protection; invalid policy is reported while safe redaction remains active. (#173471) Thanks @​skyzhao1223 and @​RomneyDa.
  • Secret egress: reject chains relying on the distrusted emSign ECC G3 root in the managed proxy and exported subprocess CA bundle; restart the Gateway after updating, and update clients with independent trust stores separately. (#179249) Thanks @​RomneyDa.
  • macOS connectivity: configured credentials take precedence over stale app environment, typed environment secret references resolve correctly, and remote Settings respects the Control UI base path. (#191468, #185141, #128175) Fixes #164596 Thanks @​RomneyDa, @​anmol0b, and @​goldmar.
  • Mac tools and messaging: iMessage remains usable after app updates without re-granting Automation, Peekaboo window inspection accepts valid snapshot references, and node exec preserves results for commands configured without a timeout. (#186107, #172116, #190729) Fixes #178719 Thanks @​aniketkrs, @​RomneyDa, @​anmol0b, @​SharkeyDev, @​holgergruenhagen, @​LiuwqGit, and @​etzelm.
  • Mac voice and embedded pages: avoid duplicate voice sends and false sent feedback, and show a recoverable load error instead of a blank or stale Mac tab. (#186271, #185432) Thanks @​anmol0b, @​etzelm, and @​RomneyDa.
  • Native voice and capture: iOS and macOS Talk tolerate slow audio acknowledgments within bounded buffering, long meeting replies are not cut off merely because generation outruns playback, and oversized Mac recordings fail with size guidance instead of dropping the node connection. Thanks @​MertBasar0, @​anmol0b, @​shakkernerd, @​kybrcore, @​sukhdeepjohar, @​potoior, and @​RomneyDa.
  • Android and desktop compatibility: Android Chat waits for the role-allowed agent list after switching Gateways, and independently updated Mac nodes can return optional cursor coordinates without a computer-use contract error. Thanks @​MertBasar0, @​anmol0b, @​shakkernerd, @​kybrcore, @​sukhdeepjohar, @​potoior, @​RomneyDa.
  • Channel recovery: Slack detects dead relay connections without treating ordinary silence as failure, Tlon reconnects stalled streams so unacknowledged events can replay, and managed Tailscale exposure recovers after a daemon restart while local authenticated access stays available. Thanks @​RomneyDa.
  • Channel delivery: Feishu keeps text from before and after tool calls in the same streaming card; Synology confirms delivery only from recipient-matched message IDs; Twitch targets and Zalo unsupported-event text follow their channel handling rather than silently losing usable content. Thanks @​RomneyDa.
  • Channel credentials and notices: implicit Slack default accounts retain complete top-level credentials alongside named accounts, channel secret consumers respect account activation, and Nostr reports failed pairing notifications without undoing approval. Thanks @​RomneyDa.
  • iMessage storage: recovery cursor keys no longer contain a PostgreSQL-incompatible NUL separator, allowing the channel to start with PostgreSQL-backed state. (#184919) Fixes #184862 Thanks @​duyufansh2008, @​RomneyDa, and @​etzelm.
  • Session and agent authority: deleting one agent no longer breaks other agents' tool authority, and local session-capability changes stop inappropriate provider fallback instead of trying every model. (#174918, #179312) Fixes #179290 Thanks @​steipete, @​chelsealong, @​obviyus, and @​Marvinthebored.
  • Prompt caching: session tool definitions stay stable across turns, including completions, heartbeats, and non-owner requests, avoiding unnecessary prompt-cache misses. (#175309, #176167) Thanks @​obviyus.
  • Conversation recovery: compaction retains the active human request across repeated summaries; queue overflow summaries retain each visible sender and conversation context; exec completion guidance survives overflow. (#180214, #187833, #190698, #182188, #184216) Thanks @​RomneyDa and @​aniketkrs.
  • Codex continuity: conversation-wide restrictions retain compatible native threads, temporary restrictions preserve the ordinary conversation binding, and a missing thread with recorded history reports an error instead of silently starting over. Thanks @​skyzhao1223 and @​RomneyDa.
  • Codex replies: transient retries can summarize the original request and completed tools without rerunning them; terminal handoffs allow already-submitted steering a bounded chance to confirm consumption and do not automatically replay uncertain input. (#183077, #184062, #181839, #167390) Thanks @​RomneyDa.
  • Shared credentials and model availability: concurrent MCP callers can reuse a fresh OAuth token without unnecessary exclusive locking, rate-limit cooldowns follow provider timing instead of accumulating hours of local backoff, and fresh model publications replace superseded refresh results. (#179997, #180280, #179144) Thanks @​RomneyDa.
  • Claude CLI and scheduled work: canceled cron runs stop reply hooks, interrupted long-running jobs no longer prevent scheduler startup, oversized or invalid CLI streams cancel their subprocess promptly, and managed completions retain the policy-filtered tool catalog. (#181245, #191422, #159931, #172026) Thanks @​steipete and @​fuller-stack-dev.
  • Session history and memory: long transcript decoding releases database read snapshots promptly, bounded history pages keep their requested anchors and adjacent messages, and memory indexing waits for archived transcript materialization. (#164442, #172970, #177937, #182091, #190182, #189284, #188450, #188483, #190690) Fixes #171467 Thanks @​RomneyDa, and @​etzelm.
  • Subagent and restart recovery: live descendants keep their expired parents available for communication, accepted yields settle sibling tool results before handoff, and stale interrupted input no longer blocks a new human message indefinitely. (#179057, #184021, #180853, #181871, #178888, #184041, #184069, #172959) Thanks @​RomneyDa.
  • Agent handoffs: waiting session sends recover the stored long reply instead of returning only a short lifecycle preview, and ACP-created sessions retain the requested working directory for later prompts. (#178271, #176852) Thanks @​RomneyDa.
  • Control UI recovery: silently dead Gateway connections reconnect without replaying uncertain sends, consumed slash-steering messages leave the queue, and routine restart notices stay concise. (#179101, #178642, #180024, #172843) Thanks @​RomneyDa.

... (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
  • 4ffdd20 test(release): supply the state script to manifest writer proofs
  • d285b6a ci(release): route FRV state operations to admitted tooling
  • b8fbe16 test: widen hosted cold-start limits for durability and voice-call proofs
  • ec5d8d2 test(workers): format the aged memo clock import
  • 3a4983e fix(test): report HTTP status when cache probes fail
  • c16f7a9 test(workers): age fixture ctimes for memo reuse proofs
  • ef14ea4 chore(release): attest 2026.11.1 candidate
  • 5a44cd1 fix(release): shorten branch push preflight (#188743)
  • adbc189 refactor: split oversized backport modules
  • ea0a7c8 fix(agents): honor user constraints during response recovery
  • 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.1.
- [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.1)

---
updated-dependencies:
- dependency-name: "@openclaw/google-meet"
  dependency-version: 2026.11.1
  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 8, 2026
@clawsweeper

clawsweeper Bot commented Nov 8, 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 8, 2026
@clawsweeper

clawsweeper Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Codex review: blocked before merge.

What this changes

This PR updates the Google Meet fixture fallback to 2026.11.1, including bundled TypeBox and host compatibility metadata.

Example: Crabpot cannot resolve the configured Google Meet npm tag.

  • Before: The fallback selects @openclaw/google-meet@2026.10.9.
  • After: The fallback selects @openclaw/google-meet@2026.11.1.

Review scores

Measure Result What it means
Overall readiness 🦪 silver shellfish (2/6) A focused dependency update with a definite provenance defect and an unresolved owner selection.
Proof confidence 🌊 off-meta tidepool Not applicable: This Dependabot maintenance PR is outside the ordinary contributor proof gate; archive inspection verifies package identity and metadata, while the successful isolated CI job does not independently prove the fallback scenario.
Patch quality 🦪 silver shellfish (2/6) 1 actionable review finding remain.

Product

Kind: Maintenance · Worth it: Needs a maintainer decision · Fix scope: Complete
User problem: Crabpot's reviewed Google Meet fallback trails the newly published plugin release.
Reason: The documented impact bar requires a useful fixture benefit, and the current owner-approved fallback pairing does not authorize this release's higher host requirement.

Merge readiness

⛔ Blocked before merge - 2 items remain

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

Priority: P2
Reviewed head: b46f7e09e43a9cabe4520bdf93754c7a4e5e1ff4
Owner decision: Required. See Decision needed.

Decision needed

  • Question: Should the reviewed Google Meet fallback advance to 2026.11.1 with its higher declared host requirement?
  • Recommendation: Qualify and adopt 2026.11.1: Identify the useful fixture coverage, repair publication-source pairing, and qualify the fallback while keeping existing host incompatibilities visible.
  • Why: The artifact contains substantive changes, but prior qualification selected 2026.10.9 and does not establish this release's fixture value or accept its higher host requirement.

Before merge

  • Update both source references with the fallback version (P2) - When tag resolution falls back to 2026.11.1, neither the registry metadata nor package supplies gitHead. scripts/report-lib.mjs then matches the payload version against this changed shim pin and uses crabpot.config.json's retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, which docs/operations.md identifies as prepared source for 2026.10.9. Reports consequently attribute the changed package to the wrong source revision. Verify the prepared source through publication qualification and update both the manifest reference and this shim's sourceRef together.
  • Explain or restore the original intent of Google Meet fallback artifact and source pairing - aa34909: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 qualified the 2026.10.9 package and paired its prepared source references while preserving moving-track and host selections.

Findings

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

Provenance

Tests

  • Missing end-to-end proof: Existing moving-track CI does not establish execution of the pinned 2026.11.1 fallback when tag resolution fails.
Agent review details

How this fits together

Crabpot resolves plugin artifacts from fixture configuration, inspects their contracts, and produces compatibility reports with upstream source links.

flowchart TD
  A[Fixture configuration] --> 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:

If the owner selects 2026.11.1, pair the fallback with verified publication-derived source references and refresh the affected report expectations.

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

Source inspection and archive metadata establish that a materialized 2026.11.1 payload 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 package-and-lock update is appropriately small, but incomplete because the existing provenance owner requires matching artifact and source references.

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.1, neither the registry metadata nor package supplies gitHead. scripts/report-lib.mjs then matches the payload version against this changed shim pin and uses crabpot.config.json's retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, which docs/operations.md identifies as prepared source for 2026.10.9. Reports consequently attribute the changed package to the wrong source revision. Verify the prepared source through publication qualification and update both the manifest reference and this shim's sourceRef together.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.98

AGENTS.md: found and applied where relevant.

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

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

  • Exact introduced change: The pinned diff updates only the package and lockfile from 2026.10.9 to 2026.11.1; both source references remain 8b18b5578f66eab1501cba4cef2310d88bfb9a41. (plugins/google-meet/package.json:7, b46f7e09e43a)
  • Reachable incorrect report attribution: readPackagePayloadSourceRef supplies the shim version and manifest source reference to packageEvidenceRef, which uses that reference when the payload version matches and gitHead is absent. (scripts/report-lib.mjs:330, 4907a46607cc)
  • Source-pairing contract and original intent: Operations guidance requires manifest and shim source references to match the published artifact and identifies the retained revision as prepared source for 2026.10.9; chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 deliberately qualified and updated those inputs together. (docs/operations.md:50, aa349094d146)
  • Published dependency inspection: Read-only inspection of the 2026.10.9 and 2026.11.1 npm archives verified their SHA-512 integrity values. The new artifact and registry metadata omit gitHead; the artifact updates TypeBox to 1.3.35, raises peer and plugin API requirements to >=2026.11.1, and changes CLI/runtime chunks. Neither package declares lifecycle scripts.
  • Applicable dependency boundary: Crabpot materializes and executes this package, so its runtime contract applies. The complete root and extensions AGENTS.md files were read at v2026.11.1; extensions policy states that first-party plugins release with the current host, without older-host fallbacks. The tag commit is policy context, not verified prepared-package provenance. (extensions/AGENTS.md, 4ffdd2047d19)
  • Owner impact policy: docs/operations.md requires a useful release, seam, compatibility, or migration benefit; the linked MEMBER decision at chore(deps): bump @openclaw/brave-plugin from 2026.10.3 to 2026.10.4 in /plugins/brave-plugin #528 (comment) declines an otherwise unnecessary host-floor increase. No owner decision selecting this Google Meet release appears in this PR. (docs/operations.md:43, 4907a46607cc)

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.

Root-cause cluster

Relationship: canonical
Canonical: #775
Summary: This PR replaces the earlier Google Meet fallback update, which Dependabot explicitly closed as superseded.

Members:

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Labels

Label changes:

  • add P2: The defect affects one fallback fixture's report attribution, without an established urgent runtime outage.
  • add merge-risk: 🚨 compatibility: The published artifact raises its peer and plugin API requirement from >=2026.10.9 to >=2026.11.1; the pinned host was already outside the previous range, so that existing mismatch is not introduced by this PR.
  • 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: The defect affects one fallback fixture's report attribution, without an established urgent runtime outage.
  • merge-risk: 🚨 compatibility: The published artifact raises its peer and plugin API requirement from >=2026.10.9 to >=2026.11.1; the pinned host was already outside the previous range, so that existing mismatch is not introduced by this PR.
  • 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 8, 2026, 4:36 AM ET / 09:36 UTC.

@vincentkoc

Copy link
Copy Markdown
Member

Closing this @openclaw/google-meet@2026.11.1 update because it is incompatible with the currently qualified host.

The Default Track pin selects OpenClaw 5f84c5b8a9889ab7035c197bc25bbe0aa8a20765 (2026.10.6). This package declares native openclaw.compat.pluginApi: ">=2026.11.1"; the pinned host’s admission policy skips it. The optional npm peer does not waive that gate.

Reconsider after an eligible immutable host completes full-corpus and three-platform qualification, its source pin is promoted through review, and the exact package cohort is qualified. Tracked in #780. Publication provenance alone is not runtime compatibility evidence.

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.

1 participant