Repository navigation
chore(deps): bump @openclaw/google-meet from 2026.10.9 to 2026.11.2 in /plugins/google-meet - #807
Conversation
Bumps [@openclaw/google-meet](https://github.com/openclaw/openclaw) from 2026.10.9 to 2026.11.2. - [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.2) --- updated-dependencies: - dependency-name: "@openclaw/google-meet" dependency-version: 2026.11.2 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 changesThis PR updates the Google Meet fixture fallback package and lockfile from 2026.10.9 to 2026.11.2. Example: The Google Meet package tag cannot be resolved.
Review scores
ProductKind: Maintenance · Worth it: No · Fix scope: Complete Merge readiness⛔ Blocked before merge - 4 items remain Keep open: main retains 2026.10.9, so the permitted close condition is unmet; this PR also introduces incorrect source attribution and remains blocked by the recorded host-qualification prerequisite. Priority: P2 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherCrabpot resolves configured plugin packages, materializes fallback artifacts when needed, and inspects their contracts to produce compatibility reports and 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]
Technical reviewBest possible solution: Retain the reviewed fallback until the recorded host prerequisite is complete, then qualify 2026.11.2 with publication-derived source references and refreshed report expectations. Do we have a high-confidence way to reproduce the issue? Source and archive metadata establish that a materialized 2026.11.2 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 package-and-lock update uses the existing owner, but it is incomplete without matching source references and premature under the recorded host-qualification decision. 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 11, 2026, 4:39 AM ET / 09:39 UTC. |
|
Closing this unqualified fallback update pending #780. The exact registry manifest requires plugin API >=2026.11.2, while Crabpot’s qualified Default Track host remains 2026.10.6. Native host admission skips this incompatible package; a green report against a moving artifact does not qualify this fallback. After the separately owned host qualification/promotion, the cohort can be refreshed together with verified publication-source references. The current fallback and source pins are retained. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @openclaw/google-meet from 2026.10.9 to 2026.11.2.
Release notes
Sourced from @openclaw/google-meet's releases.
... (truncated)
Changelog
Sourced from @openclaw/google-meet's changelog.
... (truncated)
Commits
b556fdftest: keep archive lifecycle fixtures out of age maintenanceaa20474test: wait for explicit native catalog discovery readinessf46f008test(macos): synchronize stalled navigation and report stop state31efa7atest: keep simulated Darwin listeners outside Linux client portsb4c7fe5test: clean up late durability dispatches after RPC failure1a6914ctest: distinguish CLI completion reply from early child mention46bcb1ctest: pass voice fallback agent runtime in correct slot62e4cc1test: establish legacy exec dispatch before timeout9cfe377test: use explicit boolean coercion in durability diagnostics5534c90test: format durability phase diagnosticsDependabot 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)