chore: librarian release pull request: 20251113T034326Z

[cpriti-os]

PR created by the Librarian CLI to initialize a release. Merging this PR will auto trigger a release.

Librarian Version: v1.0.0
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-go@sha256:c4bb601f466f857040028f81c47ecf808034fcf8463166320f80be761653d167

storage: 1.57.2

1.57.2 (2025-11-13)

Features

Bug Fixes

• add env var to allow disabling bound token (fix(storage): add env var to allow disabling bound token #13236) (cdaf6a6d)

Documentation

• updates to docs and docs formatting (PiperOrigin-RevId: 828488192) (93ca68d5)

[gemini-code-assist]

Summary of Changes

Hello @cpriti-os, I'm Gemini Code Assist¹! 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, automatically generated by the Librarian CLI, prepares for the release of version 1.57.2 of the storage library. It integrates a new feature that exposes specific fields for bucket listing, addresses a bug related to bound token disabling, and includes general documentation enhancements. Merging this PR will automatically trigger the official release.

Highlights

• Automated Release: This pull request is an automated release initiated by the Librarian CLI to prepare for a new version of the storage library.
• Storage Library Version Update: The storage library is being updated from version 1.57.1 to 1.57.2.
• New Feature: The update includes making return_partial_success and unreachable fields public for the list Bucket operation.
• Bug Fix: A bug fix has been added to allow disabling bound tokens via an environment variable.
• Documentation Updates: Various documentation updates and formatting improvements are also part of this release.

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]

Code Review

This pull request is an automated release for the storage module, bumping its version to 1.57.2. The changes correctly update the version number in various configuration and metadata files, including .librarian/state.yaml, snippet metadata, and storage/internal/version.go. The changelog storage/CHANGES.md has also been updated with the details of this new release. The changes are consistent and look correct for an automated release process. I find no issues with this pull request.