chore: librarian release pull request: 20251203T063934Z

[krishnamd-jkp]

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

Librarian Version: v0.7.0
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-go@sha256:718167d5c23ed389b41f617b3a00ac839bdd938a6bd2d48ae0c2f1fa51ab1c3d

storage: 1.58.0

1.58.0 (2025-12-03)

Features

• add object contexts in Go GCS SDK (feat(storage): add object contexts in Go GCS SDK #13390) (079c4d96)

• calculate crc32c by default and pass checksum in trailing and per-chunk request (feat(storage): calculate crc32c by default and pass checksum in trailing and per-chunk request #13205) (2ab1c778)

• add support for partial success in ListBuckets (feat(storage): add support for partial success in ListBuckets #13320) (d91e47f2)

Bug Fixes

• omit empty filter in http list object request (fix: omit empty filter in http list object request #13434) (377eb13b)

[gemini-code-assist]

Summary of Changes

Hello @krishnamd-jkp, 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 is an automated release initiated by the Librarian CLI to update the storage module to version 1.58.0. This update incorporates several new features, such as enhanced object context handling, improved checksum calculations, and better support for listing buckets, alongside a crucial bug fix. Merging this PR will automatically trigger the release process for the updated module.

Highlights

• Storage Module Update: The storage module has been updated to version 1.58.0.
• New Features: This release introduces new features including the addition of object contexts in the Go GCS SDK, default CRC32C calculation with checksum passing in trailing and per-chunk requests, and support for partial success in ListBuckets.
• Bug Fix: A bug has been fixed to correctly omit empty filters in HTTP list object requests.

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 PR from the Librarian CLI, bumping the version of the storage module to 1.58.0. The changes include updating version numbers in configuration files, the Go version constant, and adding a new entry to the changelog. The changes are appropriate for a release. I have one suggestion to improve the changelog's readability by sorting the entries.