chore: librarian update image pull request: 20260310T162647Z#16063
chore: librarian update image pull request: 20260310T162647Z#16063
Conversation
…prod/images-prod/python-librarian-generator@sha256:701bd1403bebb772cbc1835dc7a88aea5a07638222363534f0282bb1275b93c6
|
One or more libraries have failed to generate, please review PR description for a list of failed libraries. |
Summary of ChangesHello, 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 primarily focuses on maintaining the project's infrastructure and client library consistency. It updates the core librarian image, refines Python version compatibility, and modernizes dependency management. Significant changes were also made to client and transport classes across various services, enhancing API endpoint handling and operation request processing. Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request appears to be an automated update from the librarian tool, refreshing the generator image and regenerating client code. The changes include dropping support for Python 3.7 and 3.8, updating dependencies, adding type hints, and fixing a potential AttributeError in _get_default_mtls_endpoint. Overall, these are positive improvements. However, I've identified a couple of inconsistencies in the constraints-3.9.txt files where dependency versions are not pinned to the correct lower bounds as specified in the corresponding setup.py files. I've left specific comments with suggestions to correct these.
Note: Security Review did not run due to the size of the PR.
| google-api-core==2.21.0 | ||
| google-auth==2.35.0 |
There was a problem hiding this comment.
The versions for google-api-core and google-auth in this constraints file do not appear to match the lower bounds specified in setup.py. According to the comment in this file, these should be pinned to their lower bounds.
google-api-coreshould be2.11.0(fromsetup.py:google-api-core[grpc] >= 2.11.0, <3.0.0).google-authshould be2.14.1(fromsetup.py:google-auth >= 2.14.1, <3.0.0,...).
Please update these to reflect the correct lower bounds.
google-api-core==2.11.0
google-auth==2.14.1
| google-api-core==2.21.0 | ||
| google-auth==2.35.0 |
There was a problem hiding this comment.
The versions for google-api-core and google-auth in this constraints file do not appear to match the lower bounds specified in setup.py. According to the comment in this file, these should be pinned to their lower bounds.
google-api-coreshould be2.11.0(fromsetup.py:google-api-core[grpc] >= 2.11.0, <3.0.0).google-authshould be2.14.1(fromsetup.py:google-auth >= 2.14.1, <3.0.0,...).
Please update these to reflect the correct lower bounds.
google-api-core==2.11.0
google-auth==2.14.1
feat: update image to us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:701bd1403bebb772cbc1835dc7a88aea5a07638222363534f0282bb1275b93c6
Generation failed for