Skip to content

Sync/upstream 2026 03 10#102

Merged
linfangw merged 312 commits into
mainfrom
sync/upstream-2026-03-10
Mar 10, 2026
Merged

Sync/upstream 2026 03 10#102
linfangw merged 312 commits into
mainfrom
sync/upstream-2026-03-10

Conversation

@linfangw

Copy link
Copy Markdown
Member

No description provided.

altaywtf and others added 30 commits March 8, 2026 19:10
* CLI: include commit hash in --version output

* fix(version): harden commit SHA resolution and keep output consistent

* CLI: keep install checks compatible with commit-tagged version output

* fix(cli): include commit hash in root version fast path

* test(cli): allow null commit-hash mocks

* Installer: share version parser across install scripts

* Installer: avoid sourcing helpers from stdin cwd

* CLI: note commit-tagged version output

* CLI: anchor commit hash resolution to module root

* CLI: harden commit hash resolution

* CLI: fix commit hash lookup edge cases

* CLI: prefer live git metadata in dev builds

* CLI: keep git lookup inside package root

* Infra: tolerate invalid moduleUrl hints

* CLI: cache baked commit metadata fallbacks

* CLI: align changelog attribution with prep gate

* CLI: restore changelog contributor credit

---------

Co-authored-by: echoVic <echovic@163.com>
Co-authored-by: echoVic <echoVic@users.noreply.github.com>
Merged via squash.

Prepared head SHA: a3d6d6c
Co-authored-by: starbuck100 <25417736+starbuck100@users.noreply.github.com>
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com>
Reviewed-by: @jalehman
)

Merged via squash.

Prepared head SHA: bac2df4
Co-authored-by: yuweuii <82372187+yuweuii@users.noreply.github.com>
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com>
Reviewed-by: @jalehman
* fix: prefer bundled channel plugins over npm duplicates

* fix: tighten bundled plugin review follow-ups

* fix: address check gate follow-ups

* docs: add changelog for bundled plugin install fix

* fix: align lifecycle test formatting with CI oxfmt
…penclaw#40111)

Merged via squash.

Prepared head SHA: c651f07
Co-authored-by: remusao <1299873+remusao@users.noreply.github.com>
Co-authored-by: gumadeiras <5599352+gumadeiras@users.noreply.github.com>
Reviewed-by: @gumadeiras
mbelinky and others added 25 commits March 9, 2026 22:40
Merged via squash.

Prepared head SHA: 514d587
Co-authored-by: mbelinky <132747814+mbelinky@users.noreply.github.com>
Co-authored-by: mbelinky <132747814+mbelinky@users.noreply.github.com>
Reviewed-by: @mbelinky
Merged via squash.

Prepared head SHA: bbc4254
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Reviewed-by: @altaywtf
Merged via squash.

Prepared head SHA: 7d167df
Co-authored-by: mbelinky <132747814+mbelinky@users.noreply.github.com>
Co-authored-by: mbelinky <132747814+mbelinky@users.noreply.github.com>
Reviewed-by: @mbelinky
Merged via squash.

Prepared head SHA: 852469c
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Reviewed-by: @altaywtf
…mas (openclaw#41477)

Merged via squash.

Prepared head SHA: cae0aaf
Co-authored-by: mbelinky <132747814+mbelinky@users.noreply.github.com>
Co-authored-by: mbelinky <132747814+mbelinky@users.noreply.github.com>
Reviewed-by: @mbelinky
…nclaw#40133)

Merged via squash.

Prepared head SHA: 031d032
Co-authored-by: rbutera <6047293+rbutera@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Reviewed-by: @altaywtf
Merged via squash.

Prepared head SHA: d18356c
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Reviewed-by: @altaywtf
)

Merged via squash.

Prepared head SHA: 0053bae
Co-authored-by: zeroasterisk <23422+zeroasterisk@users.noreply.github.com>
Co-authored-by: altaywtf <9790196+altaywtf@users.noreply.github.com>
Reviewed-by: @altaywtf
…aw#41090)

Merged via squash.

Prepared head SHA: ee96e96
Co-authored-by: xinhuagu <562450+xinhuagu@users.noreply.github.com>
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com>
Reviewed-by: @jalehman
…law#40389)

Merged via squash.

Prepared head SHA: 0e600e8
Co-authored-by: Julbarth <72460857+Julbarth@users.noreply.github.com>
Co-authored-by: frankekn <4488090+frankekn@users.noreply.github.com>
Reviewed-by: @frankekn
New self-contained chat modules extracted from dashboard-v2-structure:

- chat/slash-commands.ts: slash command definitions and completions
- chat/slash-command-executor.ts: execute slash commands via gateway RPC
- chat/slash-command-executor.node.test.ts: test coverage
- chat/speech.ts: speech-to-text (STT) support
- chat/input-history.ts: per-session input history navigation
- chat/pinned-messages.ts: pinned message management
- chat/deleted-messages.ts: deleted message tracking
- chat/export.ts: shared exportChatMarkdown helper
- chat-export.ts: re-export shim for backwards compat

Gateway fix:
- Restore usage/cost stripping in chat.history sanitization
- Add test coverage for sanitization behavior

These modules are additive and tree-shaken — no existing code
imports them yet. They will be wired in subsequent slices.
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
- export.ts: handle array content blocks (Claude API format) instead
  of silently exporting empty strings
- slash-command-executor.ts: restrict /kill all to current session's
  subagent subtree instead of all sessions globally
- slash-command-executor.ts: only count truly aborted runs (check
  aborted !== false) in /kill summary
Merged via squash.

Prepared head SHA: 1e6f1d9
Co-authored-by: zheliu2 <15888718+zheliu2@users.noreply.github.com>
Co-authored-by: obviyus <22031114+obviyus@users.noreply.github.com>
Reviewed-by: @obviyus
Merged via squash.

Prepared head SHA: f243379
Co-authored-by: huntharo <5617868+huntharo@users.noreply.github.com>
Co-authored-by: huntharo <5617868+huntharo@users.noreply.github.com>
Reviewed-by: @huntharo
@linfangw linfangw merged commit 81000b7 into main Mar 10, 2026
2 of 10 checks passed
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates a wide array of upstream changes, significantly updating the Android and iOS mobile applications by streamlining their feature sets and permissions. It also enhances development tooling with new security scanning configurations and clearer contribution guidelines. Furthermore, the update includes numerous bug fixes and feature additions across various components, all reflected in comprehensive documentation revisions.

Highlights

  • Android App Refinements: Removed self-update functionality, screen recording, and background location permissions and related code from the Android application, focusing on foreground operation for voice and location features.
  • iOS App Enhancements: Updated version strings, introduced new Swift files for WatchReplyCoordinator and TalkMode configuration parsing, and improved Canvas host URL resolution and pending foreground action handling.
  • Security and Code Quality Tools: Added a new pattern to ignore Sparkle appcast signatures in .detect-secrets.cfg, included a new CodeQL configuration for JavaScript/TypeScript, and updated pre-commit hooks and .secrets.baseline.
  • Developer Workflow Improvements: Updated the pull request template and contributing guidelines to include clear instructions for handling bot review conversations and added new maintainers to the project.
  • Changelog and Documentation Updates: The changelog was updated with numerous unreleased changes and fixes, including cron job migration, ACP improvements, and various bug fixes across platforms and channels. Extensive documentation revisions were made to reflect these changes, covering mobile node features, web search providers, ACP bridge scope, and CLI commands like backup and doctor.
  • Docker Build Optimizations: Modified Dockerfiles to incorporate build cache mounts, normalize extension permissions, and update build commands for more efficient and secure container builds.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
Ignored Files
  • Ignored by pattern: .github/workflows/** (5)
    • .github/workflows/auto-response.yml
    • .github/workflows/ci.yml
    • .github/workflows/codeql.yml
    • .github/workflows/docker-release.yml
    • .github/workflows/labeler.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request appears to be a large synchronization from an upstream repository, introducing a wide range of changes across the project. Key changes include significant feature removals from the Android application, likely for Google Play Store compliance, such as self-updates, screen recording, and background location access. The codebase has been substantially refactored for better maintainability and consistency, particularly in the handling of talk mode configuration and voice resolution, with shared logic moved into the OpenClawKit. Dockerfiles have been modernized using BuildKit features for improved caching and smaller image sizes. Reliability has been enhanced in the iOS app and Chrome extension through better state management and error handling. The documentation has been extensively updated to reflect all these changes. Overall, the changes are of high quality, well-structured, and represent a significant improvement to the project's health and maintainability. I have not identified any issues that meet the required severity threshold for comments.

Note: Security Review did not run due to the size of the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.