Skip to content

Comments

docs(release): update changelog for the 2026-02-24 release#15997

Merged
scotthart merged 1 commit intogoogleapis:mainfrom
scotthart:release_20260224_changelog
Feb 24, 2026
Merged

docs(release): update changelog for the 2026-02-24 release#15997
scotthart merged 1 commit intogoogleapis:mainfrom
scotthart:release_20260224_changelog

Conversation

@scotthart
Copy link
Member

@scotthart scotthart commented Feb 24, 2026

This change is Reviewable

@gemini-code-assist
Copy link

Summary of Changes

Hello @scotthart, 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 versioning for the v3.2.0 release by removing pre-release indicators across the codebase. Concurrently, the changelog has been updated to document the new features introduced in the Cloud Key Management Service for this release, ensuring that the project's version information and release notes are accurate and up-to-date.

Highlights

  • Changelog Update: The CHANGELOG.md file has been updated to reflect the v3.2.0 release, including new features for the Cloud Key Management Service.
  • Release Candidate Tag Removal: The 'rc' (release candidate) tag has been removed from various versioning files, indicating a transition from a release candidate to a stable release.
Changelog
  • CHANGELOG.md
    • Updated the v3.2.0 entry to include the release date.
    • Added new features for Cloud Key Management Service, including DeleteCryptoKey and DeleteCryptoKeyVersion RPCs.
    • Introduced the RetiredResource resource and associated ListRetiredResources and GetRetiredResource RPCs.
  • CMakeLists.txt
    • Removed the rc pre-release tag from PROJECT_VERSION_PRE_RELEASE.
  • MODULE.bazel
    • Updated the module version from 3.2.0-rc to 3.2.0.
  • google/cloud/internal/version_info.h
    • Cleared the GOOGLE_CLOUD_CPP_VERSION_PRE_RELEASE macro from rc to an empty string.
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 the v3.2.0 release. The changes include updating the CHANGELOG.md with the release date and new features for Cloud Key Management Service, and removing the rc (release candidate) pre-release identifier from the version in the build files (CMakeLists.txt, MODULE.bazel, and google/cloud/internal/version_info.h). The changes are consistent and correct for a release.

@scotthart scotthart enabled auto-merge (squash) February 24, 2026 16:55
@codecov
Copy link

codecov bot commented Feb 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.64%. Comparing base (860c4a8) to head (585502d).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15997      +/-   ##
==========================================
+ Coverage   92.63%   92.64%   +0.01%     
==========================================
  Files        2334     2334              
  Lines      214635   214633       -2     
==========================================
+ Hits       198823   198845      +22     
+ Misses      15812    15788      -24     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@scotthart scotthart merged commit 85deaa7 into googleapis:main Feb 24, 2026
57 of 64 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