Permalink
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 5 commits
- 4 files changed
- 3 contributors
Commits on Aug 12, 2026
-
chore: release this candidate as 2.7.0
The only breaking marker in this range is a packaging change: pyarrow moved out of the gcp extra into a new bigquery-analytics extra. Users keep their >=2,<3 pins, and the artifact check keeps a baseline to compare against. Release-As: 2.7.0
Commits on Aug 13, 2026
-
Sync release/candidate with main for the 2.7.0 release
The candidate was cut yesterday and the release slipped a day, so it no longer carried everything on main. This takes main's tree wholesale and keeps the Release-As footer that pins the version to 2.7.0.
-
Sync release/candidate with main for the 2.7.0 release
Picks up the DNS rebinding guard on the local API server and media in tool responses for non-Gemini models, both of which landed after the first sync.
-
chore(release/candidate): release 2.7.0 (#6700)
Co-authored-by: George Weale <51099682+GWeale@users.noreply.github.com>
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...release/v2.7.0