Repository navigation
chore(deps): bump @openclaw/google-meet from 2026.10.9 to 2026.11.3 in /plugins/google-meet - #832
Conversation
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>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: blocked before merge. What this changesUpdates 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.
Review scores
ProductKind: Maintenance · Worth it: No · Fix scope: Complete 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 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherCrabpot 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]
Technical reviewBest 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:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 90b39250dd03. Merge-risk optionsMaintainer options:
Provenance checked
TestingProof path: none. SecurityNone. EvidenceWhat I checked:
Likely related people:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel changes:
Label justifications:
Rating scale6/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. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed November 14, 2026, 4:37 AM ET / 09:37 UTC. |
|
Superseded by #860. |
Bumps @openclaw/google-meet from 2026.10.9 to 2026.11.3.
Release notes
Sourced from @openclaw/google-meet's releases.
... (truncated)
Changelog
Sourced from @openclaw/google-meet's changelog.
... (truncated)
Commits
847611dfix(gateway): settle ACP lifecycle before completion replaydba4a3dfix(update): recover interrupted managed updates on 2026.11.3 (#193884)70abf44fix(sessions): isolate private transcript read dispatchd7154a9test(live): use short random tool probe nonces (#172737)23fa333fix(sessions): capture physical read proof after queued admission3a31314test(sessions): admit schema probe fixture writes behind maintenancec998519fix(gateway): keep idle replay lookup off history lane3ac9ee0fix(gateway): replay consumed collected inputs after idle6de33ecfix(sessions): avoid worker OOM during large transcript index repairfd8dd65docs: check hotfix ledger completeness at release closeout (#196355)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)