chore: bump versions for google-cloud-access-context-manager, google-cloud-kms and google-cloud-os-config

[parthea]

Bump the minimum version of google-cloud-access-context-manager, google-cloud-kms and google-cloud-os-config to the version which doesn't have a runtime dependency on setuptools to avoid the following error which appears in googleapis/google-cloud-python#16094. See build log

2026-03-12T23:09:35.5805063Z     import pkg_resources
2026-03-12T23:09:35.5805409Z E   ModuleNotFoundError: No module named 'pkg_resources'

https://github.com/googleapis/python-access-context-manager/releases/tag/v0.2.0
https://github.com/googleapis/python-kms/releases/tag/v2.13.0
https://github.com/googleapis/python-os-config/releases/tag/v1.13.0

[gemini-code-assist]

Summary of Changes

Hello, 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 updates the minimum required versions for several Google Cloud client libraries within the _pypi_packages.j2 template. The change specifically targets google-cloud-access-context-manager, google-cloud-kms, and google-cloud-os-config to newer versions that eliminate a critical runtime dependency on setuptools's pkg_resources module, thereby preventing ModuleNotFoundError exceptions during execution.

Highlights

• Dependency Version Bumps: Increased the minimum required versions for google-cloud-access-context-manager, google-cloud-kms, and google-cloud-os-config to address a known runtime issue.
• Runtime Dependency Resolution: Resolved a ModuleNotFoundError: No module named 'pkg_resources' by updating package versions to those that no longer have a runtime dependency on setuptools.

Changelog

• gapic/templates/_pypi_packages.j2
  • Updated the lower bound for google-cloud-access-context-manager from 0.1.8 to 0.2.0.
  • Updated the lower bound for google-cloud-kms from 2.4.1 to 2.13.0.
  • Updated the lower bound for google-cloud-os-config from 1.3.1 to 1.13.0.

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 updates the minimum required versions for google-cloud-access-context-manager, google-cloud-kms, and google-cloud-os-config. The change is made in the gapic/templates/_pypi_packages.j2 template file to ensure that generated packages use versions that do not have a runtime dependency on setuptools, addressing a ModuleNotFoundError for pkg_resources. The modifications are correct and well-contained within the template data. I have reviewed the changes and found no issues.