Skip to content

release 2.6.1#80

Merged
lip-liu merged 2 commits intomainfrom
2-6-1
Mar 4, 2026
Merged

release 2.6.1#80
lip-liu merged 2 commits intomainfrom
2-6-1

Conversation

@lip-liu
Copy link
Collaborator

@lip-liu lip-liu commented Mar 3, 2026

No description provided.

@gemini-code-assist
Copy link

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 finalizes the release of version 2.6.1 for the BetoCQ test suite. It introduces new XCC test cases for AQT, updates the target SDK version for snippets, and refines WifiManager API access. Additionally, the project's minimum Python version requirement has been elevated to ensure compatibility with newer development environments.

Highlights

  • New Features: Added XCC test cases for AQT that do not depend on hardware capabilities.
  • SDK Update: Updated the snippet SDK target version to 35.
  • API Access: Implemented the use of an internal WifiManagerSnippet for accessing WifiManager APIs.
  • Version Bump: Incremented the project version from 2.6.0 to 2.6.1.
  • Python Requirement: Increased the minimum required Python version from 3.11 to 3.12.

🧠 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
  • betocq/nearby_connection/CHANGELOG.md
    • Added new release notes for version 2.6.1.
    • Included details about new XCC test cases for AQT.
    • Documented the update of the snippet SDK target version to 35.
    • Noted the change to use internal WifiManagerSnippet for API access.
  • build_config/nearby_connection/pyproject.toml
    • Updated the project version from 2.6.0 to 2.6.1.
    • Increased the requires-python dependency from ">=3.11" to ">=3.12".
Activity
  • No human activity has been recorded on this pull request since its creation.
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

@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 prepares for release 2.6.1 by updating the version in pyproject.toml and adding release notes to CHANGELOG.md. My review includes a correction for a typo in the changelog and a recommendation to document the Python version requirement change in the release notes for better visibility to users.

Note: Security Review has been skipped due to the limited scope of the PR.

## 2.6.1 (03/03/2026)
## New
* Add XCC test cases for AQT which have no dependency on the hardware
capabilitiy.

Choose a reason for hiding this comment

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

medium

There is a typo in "capabilitiy".

Suggested change
capabilitiy.
capability.

description = "Better Together Connectivity Quality test suite."
readme = "README.md"
requires-python = ">=3.11"
requires-python = ">=3.12"

Choose a reason for hiding this comment

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

medium

Bumping the minimum required Python version from 3.11 to 3.12 is a significant change that should be documented in the CHANGELOG.md file for this release. This helps users understand the new requirements and prepare their environments accordingly.

@lip-liu lip-liu merged commit e78ad33 into main Mar 4, 2026
2 checks passed
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.

2 participants