Skip to content

Conversation

@elliette
Copy link
Member

@elliette elliette commented Nov 7, 2025

Add release notes for the 2.51.1 hotfix version of DevTools. This is version of DevTools that is going out with Flutter 3.38.

Includes the release notes for 2.51.0 along with the release notes for the cherry-picks included in 2.51.1 (see flutter/devtools@v2.51.0...v2.51.1)

@elliette elliette requested review from a team and sfshaza2 as code owners November 7, 2025 18:05
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @elliette, 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 introduces the release notes for DevTools version 2.51.1, which is a hotfix release accompanying Flutter 3.38. The notes detail various general improvements, bug fixes in the Inspector and Network Profiler, and enhanced integration with VS Code, ensuring users are informed of the latest changes and stability improvements.

Highlights

  • General Updates: Flutter beta channel users are now opted into the DevTools-on-Wasm experiment, with other users able to enable it via settings.
  • General Updates: Horizontal scrollbars have been added to data tables for improved navigation.
  • General Updates: Data table columns can now be resized by dragging header separators.
  • Inspector Updates: An issue was fixed where selecting a widget in the Inspector incorrectly opened the widget definition file instead of the user's project file.
  • Network Profiler Updates: The layout of the 'error count' badge in the tab name has been fixed.
  • Network Profiler Updates: Display of 'Response Headers' and 'Request Headers' when no headers are present has been corrected.
  • Network Profiler Updates: A banner now clearly indicates when DevTools is not logging network requests.
  • VS Code Updates: macOS shortcuts like Cmd+C and Cmd+V now function correctly when DevTools is embedded within VS Code.
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.

Copy link
Contributor

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

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 adds the release notes for DevTools version 2.51.1. The notes are well-structured and clear. I have one suggestion to improve formatting consistency within the document.

Comment on lines 40 to 42
- On macOS, shortcuts like `Cmd`+`C` and `Cmd`+`V` now work when DevTools is
embedded inside VS Code -
[#9472](https://github.com/flutter/devtools/pull/9472)
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For consistency with other release note entries, please add a period at the end of the sentence. The current formatting with the dash on a new line is also inconsistent with other items in this list. I suggest combining this into a single line and letting it wrap naturally.

Suggested change
- On macOS, shortcuts like `Cmd`+`C` and `Cmd`+`V` now work when DevTools is
embedded inside VS Code -
[#9472](https://github.com/flutter/devtools/pull/9472)
- On macOS, shortcuts like `Cmd`+`C` and `Cmd`+`V` now work when DevTools is embedded inside VS Code. - [#9472](https://github.com/flutter/devtools/pull/9472)

@flutter-website-bot
Copy link
Collaborator

flutter-website-bot commented Nov 7, 2025

Visit the preview URL for this PR (updated for commit 754b148):

https://flutter-docs-prod--pr12659-devtools-release-notes-2-51-ap8ilcsl.web.app

Copy link
Member

@parlough parlough left a comment

Choose a reason for hiding this comment

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

Thanks!

@parlough parlough merged commit 37e377d into flutter:main Nov 7, 2025
9 checks passed
sfshaza2 pushed a commit that referenced this pull request Nov 12, 2025
Add release notes for the 2.51.1 hotfix version of DevTools. This is
version of DevTools that is going out with Flutter 3.38.

Includes the release notes for 2.51.0 along with the release notes for
the cherry-picks included in 2.51.1 (see
flutter/devtools@v2.51.0...v2.51.1)
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.

3 participants