| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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 updates the google-auth Python dependency to its latest version, v2.49.1. This ensures the project benefits from the most recent features, bug fixes, and security enhancements provided by the Google authentication library, maintaining compatibility and improving overall stability. Highlights
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.
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
|
Sorry, something went wrong.
There was a problem hiding this comment.
This pull request updates the google-auth dependency. However, the update appears to have been done manually, leading to an inconsistent requirements.txt file. The new version of google-auth does not depend on cachetools, but cachetools is still present and attributed to google-auth. The requirements.txt file should be regenerated using pip-compile to ensure the dependency tree is correct.
Sorry, something went wrong.
| google-auth==2.49.1 \ | ||
| --hash=sha256:16d40da1c3c5a0533f57d268fe72e0ebb0ae1cc3b567024122651c045d879b64 \ | ||
| --hash=sha256:195ebe3dca18eddd1b3db5edc5189b76c13e96f29e73043b923ebcf3f1a860f7 |
There was a problem hiding this comment.
While updating google-auth is a good step, this change has been applied in a way that creates an inconsistency in your dependency file.
According to the release notes, google-auth version 2.47.0 and newer dropped the cachetools dependency.
However, requirements.txt still includes cachetools and incorrectly lists it as a dependency of google-auth (lines 17-20):
cachetools==7.0.2 \
...
# via google-auth
This indicates that requirements.txt is now out of sync. Instead of manually changing the version, you should regenerate the file by running pip-compile --generate-hashes, as indicated in the file's header. This will ensure all transitive dependencies are correctly resolved.
Sorry, something went wrong.
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update (==2.49.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR contains the following updates:
Release Notes
googleapis/google-auth-library-python (google-auth)v2.48.0
Compare Source
Features
Bug Fixes
v2.47.0
Compare Source
Features
Bug Fixes
v2.46.0
Compare Source
Documentation
Features
Bug Fixes
v2.45.0
Compare Source
Features
v2.44.0
Compare Source
Features
Bug Fixes
v2.43.0
Compare Source
Features
GOOGLE_API_USE_CLIENT_CERTIFICATE is not set, when the MWID/X.509 cert
sources detected. Also, fix check_use_client_cert to return boolean
value.
Change #1848 added the check_use_client_cert method that helps know if
client cert should be used for mTLS connection. However, that was in a
private class, thus, created a public wrapper of the same function so
that it can be used by python Client Libraries. Also, updated
check_use_client_cert to return a boolean value instead of existing
string value for better readability and future scope.
--------- (1535eccbff0ad8f3fd6a9775316ac8b77dca66ba)
(either true or false), the SDK will respect that setting. This is
necessary for test scenarios and users who need to explicitly control
mTLS behavior.
set, the SDK will automatically enable mTLS only if it detects Managed
Workload Identity (MWID) or X.509 Workforce Identity Federation (WIF)
certificate sources. In other cases where the variable is not set, mTLS
will remain disabled.
** This change also adds the helper method check_use_client_cert and
it's unit test, which will be used for checking the criteria for setting
the mTLS to true
** This change is only for Auth-Library, other changes will be created
for Client-Library use-cases.
--------- (395e405b64b56ddb82ee639958c2e8056ad2e82b)
Wait for
#1819. (c503eaa511357d7a76cc1e1f1d3a3be2dabd5bca)
v2.42.1
Compare Source
Bug Fixes
v2.42.0
Compare Source
Features
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.