Skip to content

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

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

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

Release notes

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

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

Example: The configured Google Meet npm tag is unavailable.

  • Before: Crabpot selects @openclaw/google-meet@2026.10.9.
  • After: Crabpot selects @openclaw/google-meet@2026.11.4.

Review scores

Measure Result What it means
Overall readiness 🦪 silver shellfish (2/6) The dependency and lock agree, but source attribution is incorrect and the recorded host prerequisite remains unresolved.
Proof confidence 🌊 off-meta tidepool Not applicable: This Dependabot-authored fixture-input update is outside the contributor proof gate; archive inspection verifies identity and metadata without establishing runtime qualification.
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 newer fallback updates until the separately owned host-qualification prerequisite is complete.

Merge readiness

⛔ Blocked before merge - 4 items remain

Keep open: main still pins 2026.10.9, and this PR needs a source-attribution repair before it can follow the recorded host-qualification sequence.

Priority: P2
Reviewed head: 5e51dfabe920b6d54163f0019b39f223b0bce346

Before merge

  • Update both source references with the fallback version (P2) - When tag resolution falls back to 2026.11.4, neither registry metadata nor the archived package.json supplies gitHead. scripts/report-lib.mjs therefore matches the payload against this changed shim version and uses crabpot.config.json’s retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, which the prior refresh identifies 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, whose >=2026.11.4 plugin API requirement excludes the pinned 2026.10.6 host.
  • Product: not worth merging - Recorded maintainer direction defers newer fallback updates until the separately owned host-qualification prerequisite is complete.
  • 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 paired fallback versions with verified prepared-source references while preserving independent host qualification; this PR changes the version without addressing that pairing.

Findings

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

Provenance

Agent review details

How this fits together

Crabpot resolves plugin fixtures, checks their contracts against a selected OpenClaw host, and produces compatibility reports with upstream source links.

flowchart TD
  A[Fixture manifest] --> B[Package resolution]
  C[Pinned fallback shim] --> B
  B --> D[Published plugin artifact]
  D --> E[Host compatibility inspection]
  E --> F[Reports and source links]
Loading

Technical review

Best possible solution:

Retain the reviewed fallback until host qualification is complete, then update the exact package with verified matching source references.

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

Current source and integrity-checked archive metadata establish that the new fallback 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 the refresh must preserve artifact/source pairing and 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.4, neither registry metadata nor the archived package.json supplies gitHead. scripts/report-lib.mjs therefore matches the payload against this changed shim version and uses crabpot.config.json’s retained 8b18b5578f66eab1501cba4cef2310d88bfb9a41 reference, which the prior refresh identifies 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 433c97070c37.

Merge-risk options

Maintainer options:

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

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

  • Exact introduced change and current main: The pinned diff changes only the package version and corresponding lock metadata. Both source references remain 8b18b5578f66eab1501cba4cef2310d88bfb9a41. GitHub main remains 433c970 with fallback 2026.10.9. (plugins/google-meet/package.json:7, 5e51dfabe920)
  • Source-attribution consumer: readPackagePayloadSourceRef passes the shim version and manifest source reference to packageEvidenceRef, which selects that reference when the artifact version matches and no Git head is available. (scripts/report-lib.mjs:330, 433c97070c37)
  • Published artifact identity and metadata: The downloaded 2026.11.4 archive’s SHA-512 matches the PR lock. Neither registry metadata nor archived package.json supplies gitHead; the package declares pluginApi >=2026.11.4 and bundles TypeBox 1.3.35. Registry provenance was decoded, but no Sigstore verification or runtime qualification is claimed.
  • Prior package-and-source pairing: chore(deps): refresh 21 official plugin fallbacks to 2026.10.9 #653 deliberately paired the 2026.10.9 fallback with prepared source 8b18b5578f66eab1501cba4cef2310d88bfb9a41 and kept host qualification separate. (plugins/google-meet/package.json:15, aa349094d146)
  • Recorded qualification prerequisite: Qualify a newer Default Track host before refreshing official plugin fallbacks #780 remains open and specifies eligible immutable-host qualification and promotion before reconsidering newer fallback pairs; the current Default Track still selects the 2026.10.6 host. (.github/openclaw-default-track.json:3, 433c97070c37)
  • Authoritative host admission contract: The fixture is executed against this host, making its admission contract applicable. The pinned host reports 2026.10.6 and skips non-bundled plugins outside their declared plugin API range. The complete root and src/plugins AGENTS.md files were read and their contract-preservation guidance applied. (src/plugins/discovery-availability.ts:53, 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: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/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 fixture-maintenance update introduces incorrect report attribution without evidence of an urgent deployed-user outage.
  • add merge-risk: 🚨 compatibility: The replacement fallback requires plugin API >=2026.11.4 while the independently qualified Default Track host remains 2026.10.6.
  • 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 fixture-maintenance update introduces incorrect report attribution without evidence of an urgent deployed-user outage.
  • merge-risk: 🚨 compatibility: The replacement fallback requires plugin API >=2026.11.4 while the independently qualified Default Track host remains 2026.10.6.
  • 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 19, 2026, 4:39 AM ET / 09:39 UTC.

@dependabot @github

dependabot Bot commented on behalf of github Nov 20, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #882.

@dependabot dependabot Bot closed this Nov 20, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/plugins/google-meet/openclaw/google-meet-2026.11.4 branch November 20, 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