Skip to content

chore(deps): update all dependencies #1885

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
renovate-bot wants to merge 1 commit into from
Closed

chore(deps): update all dependencies #1885

renovate-bot wants to merge 1 commit into from
+5 −5

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Dec 12, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
google-auth ==2.41.1 -> ==2.45.0 age confidence
google-cloud-compute (source) ==1.5.1 -> ==1.40.0 age confidence
google-cloud-storage ==3.1.0 -> ==3.7.0 age confidence
pytest (changelog) ==8.4.2 -> ==9.0.2 age confidence
python-dotenv ==1.1.1 -> ==1.2.1 age confidence

Release Notes

googleapis/google-auth-library-python (google-auth)

v2.45.0

Compare Source

Features

v2.44.0

Compare Source

Features
Bug Fixes

v2.43.0

Compare Source

Features
  • Add public wrapper for _mtls_helper.check_use_client_cert which enables mTLS if GOOGLE_API_USE_CLIENT_CERTIFICATE is not set, when the MWID/X.509 cert sources detected (#​1859) Add public wrapper for check_use_client_cert which enables mTLS if
    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)
  • Enable mTLS if GOOGLE_API_USE_CLIENT_CERTIFICATE is not set, if the MWID/X.509 cert sources detected (#​1848) The Python SDK will use a hybrid approach for mTLS enablement:
  • If the GOOGLE_API_USE_CLIENT_CERTIFICATE environment variable is set
    (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.
  • If the GOOGLE_API_USE_CLIENT_CERTIFICATE environment variable is not
    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)

v2.42.1

Compare Source

Bug Fixes

v2.42.0

Compare Source

Features
Bug Fixes
googleapis/google-cloud-python (google-cloud-compute)

v1.40.0: google-cloud-compute 1.40.0

Compare Source

Features

v1.39.0: google-cloud-compute 1.39.0

Compare Source

Features

  • [google-cloud-compute] Update Compute Engine v1 API to revision 2025090 (4e5a0b5)

  • [google-cloud-compute] Update Compute Engine v1 API to revision 2025090 (4e5a0b5)

v1.38.0: google-cloud-compute: v1.38.0

Compare Source

Features

v1.37.0: google-cloud-compute: v1.37.0

Compare Source

Features

v1.36.0: google-cloud-compute: v1.36.0

Compare Source

Features
  • [google-cloud-compute] Update Compute Engine v1 API to revision 2025080 (51732d3)

v1.35.0: google-cloud-compute: v1.35.0

Compare Source

Features

v1.34.0: google-cloud-compute: v1.34.0

Compare Source

Features

v1.33.0: google-cloud-compute: v1.33.0

Compare Source

Features

v1.32.0: google-cloud-compute: v1.32.0

Compare Source

Features

v1.31.0: google-cloud-compute: v1.31.0

Compare Source

Features

v1.30.0: google-cloud-compute: v1.30.0

Compare Source

Features

v1.29.0: google-cloud-compute: v1.29.0

Compare Source

Features

v1.28.0: google-cloud-compute: v1.28.0

Compare Source

Features

v1.27.0

Compare Source

v1.26.0

Compare Source

v1.25.0

Compare Source

v1.24.0

Compare Source

v1.23.0

Compare Source

v1.22.0

Compare Source

v1.21.0: google-cloud-os-config: v1.21.0

Compare Source

Features
  • Add highest_upgradable_cve_severity field to Vulnerability report (e8feca7)
Documentation
  • A comment for field filter in message .google.cloud.osconfig.v1.ListVulnerabilityReportsRequest is changed (e8feca7)
  • A comment for field update_time in message .google.cloud.osconfig.v1.VulnerabilityReport is changed (e8feca7)

v1.20.1

Compare Source

v1.20.0

Compare Source

v1.19.2

Compare Source

v1.19.1

Compare Source

v1.19.0

Compare Source

v1.18.0

Compare Source

v1.17.0: google-cloud-trace 1.17.0

Compare Source

1.17.0 (2025-10-20)

v1.16.1

Compare Source

v1.16.0

Compare Source

v1.15.0: google-cloud-resource-manager 1.15.0

Compare Source

1.15.0 (2025-10-20)

v1.14.1

v1.14.0

v1.13.0

v1.12.1

v1.12.0

v1.11.0

v1.10.0

v1.9.0

v1.7.0: google-cloud-appengine-logging 1.7.0

1.7.0 (2025-10-16)

v1.6.1

v1.6.0

googleapis/python-storage (google-cloud-storage)

v3.7.0

Compare Source

Features
Bug Fixes

v3.6.0

Compare Source

Features
  • Add support for partial list buckets (#​1606) (92fc2b0)
  • Make return_partial_success and unreachable fields public for list Bucket (#​1601) (323cddd)
  • zb-experimental: Add async write object stream (5ab8103)
  • zb-experimental: Add async write object stream (#​1612) (5ab8103)
Bug Fixes

v3.5.0

Compare Source

Features
Bug Fixes
  • Deprecate credentials_file argument (74415a2)
  • Flaky system tests for resumable_media (#​1592) (7fee3dd)
  • Make download_ranges compatible with asyncio.create_task(..) (#​1591) (faf8b83)
  • Make download_ranges compatible with asyncio.create_task(..) (#​1591) (faf8b83)
  • Redact sensitive data from OTEL traces and fix env var parsing (#​1553) (a38ca19)
  • Redact sensitive data from OTEL traces and fix env var parsing (#​1553) (a38ca19)
  • Use separate header object for each upload in Transfer Manager MPU (#​1595) (0d867bd)

v3.4.1

Compare Source

Bug Fixes
  • Fixes #​1561 by adding an option to specify the entire object checksum for resumable uploads via the upload_from_string, upload_from_file, and upload_from_filename methods (acb918e)

v3.4.0

Compare Source

Features
Bug Fixes

v3.3.1

Compare Source

Bug Fixes
  • Provide option to user to set entire object checksum at "initiate a resumable upload session" and send the same (#​1525) (a8109e0)
  • Send part's checksum for XML MPU part upload (#​1529) (2ad77c7)

v3.3.0

Compare Source

Features
Bug Fixes
Documentation

v3.2.0

Compare Source

Features

v3.1.1

Compare Source

Bug Fixes
  • Add a check for partial response data (#​1487) (7e0412a)
  • Add trove classifier for Python 3.13 (0100916)
  • deps: Require google-crc32c >= 1.1.3 (0100916)
  • deps: Require protobuf >= 3.20.2, < 7.0.0 (0100916)
  • deps: Require requests >= 2.22.0 (0100916)
  • Remove setup.cfg configuration for creating universal wheels (#​1448) (d3b6b3f)
  • Resolve issue where pre-release versions of dependencies are installed (0100916)
  • Segmentation fault in tink while writing data (#​1490) (2a46c0b)
Documentation
pytest-dev/pytest (pytest)

v9.0.2

Compare Source

pytest 9.0.2 (2025-12-06)

Bug fixes

  • #​13896: The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.

    You may enable it again by passing -p terminalprogress. We may enable it by default again once compatibility improves in the future.

    Additionally, when the environment variable TERM is dumb, the escape codes are no longer emitted, even if the plugin is enabled.

  • #​13904: Fixed the TOML type of the tmp_path_retention_count settings in the API reference from number to string.

  • #​13946: The private config.inicfg attribute was changed in a breaking manner in pytest 9.0.0.
    Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
    It will be deprecated in pytest 9.1 and removed in pytest 10.

  • #​13965: Fixed quadratic-time behavior when handling unittest subtests in Python 3.10.

Improved documentation

  • #​4492: The API Reference now contains cross-reference-able documentation of pytest's command-line flags <command-line-flags>.

v9.0.1

Compare Source

pytest 9.0.1 (2025-11-12)

Bug fixes

  • #​13895: Restore support for skipping tests via raise unittest.SkipTest.
  • #​13896: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
  • #​13904: Fixed the TOML type of the verbosity settings in the API reference from number to string.
  • #​13910: Fixed UserWarning: Do not expect file_or_dir on some earlier Python 3.12 and 3.13 point versions.

Packaging updates and notes for downstreams

  • #​13933: The tox configuration has been adjusted to make sure the desired
    version string can be passed into its package_env through
    the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
    variable as a part of the release process -- by webknjaz.

Contributor-facing changes

  • #​13891, #​13942: The CI/CD part of the release automation is now capable of
    creating GitHub Releases without having a Git checkout on
    disk -- by bluetech and webknjaz.
  • #​13933: The tox configuration has been adjusted to make sure the desired
    version string can be passed into its package_env through
    the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
    variable as a part of the release process -- by webknjaz.

v9.0.0

Compare Source

pytest 9.0.0 (2025-11-05)

New features

  • #​1367: Support for subtests has been added.

    subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

    Example:

    def contains_docstring(p: Path) -> bool:
    """Return True if the given Python file contains a top-level docstring."""
    ...

def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
    for path in Path.cwd().glob("*.py"):
        with subtests.test(path=str(path)):
            assert contains_docstring(path)

    Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

    In addition, unittest.TestCase.subTest is now also supported.

    This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.

    [!NOTE]
    This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

  • #​13743: Added support for native TOML configuration files.

    While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options],
    it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
    Now, pytest supports the native TOML data model.

    In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.

    # pyproject.toml
[tool.pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

    The [tool.pytest.ini_options] table remains supported, but both tables cannot be used at the same time.

    If you prefer to use a separate configuration file, or don't use pyproject.toml, you can use pytest.toml or .pytest.toml:

    # pytest.toml or .pytest.toml
[pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

    The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

    See config file formats for full details.

  • #​13823: Added a "strict mode" enabled by the strict configuration option.

    When set to true, the strict option currently enables

    • strict_config
    • strict_markers
    • strict_parametrization_ids
    • strict_xfail

    The individual strictness options can be explicitly set to override the global strict setting.

    The previously-deprecated --strict command-line flag now enables strict mode.

    If pytest adds new strictness options in the future, they will also be enabled in strict mode.
    Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
    or if you want to proactively adopt new strictness options as they are added.

    See strict mode for more details.

  • #​13737: Added the strict_parametrization_ids configuration option.

    When set, pytest emits an error if it detects non-unique parameter set IDs,
    rather than automatically making the IDs unique by adding 0, 1, ... to them.
    This can be particularly useful for catching unintended duplicates.

  • #​13072: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence.
    When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
    you'll see the progress in the terminal tab or window,
    allowing you to monitor pytest's progress at a glance.

    This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:

    • On a user level, using -p no:terminalprogress on the command line or via an environment variable PYTEST_ADDOPTS='-p no:terminalprogress'.
    • On a project configuration level, using addopts = "-p no:terminalprogress".

  • #​478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.

    Previously, this option only impacted package imports, now it also impacts tests discovery.

  • #​13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock.

    Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process.

    -- by ogrisel.

  • #​13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.

    Plugins can now register alternative names for configuration options,
    allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
    The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.

Improvements in existing functionality

  • #​13330: Having pytest configuration spread over more than one file (for example having both a pytest.ini file and pyproject.toml with a [tool.pytest.ini_options] table) will now print a warning to make it clearer to the user that only one of them is actually used.

    -- by sgaist

  • #​13574: The single argument --version no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

    Passing --version twice (e.g., pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.

    [!NOTE]
    Since --version is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as PYTEST_ADDOPTS or addopts.

  • #​13823: Added strict_xfail as an alias to the xfail_strict option,
    strict_config as an alias to the --strict-config flag,
    and strict_markers as an alias to the --strict-markers flag.
    This makes all strictness options consistently have configuration options with the prefix strict_.

  • #​13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.

  • #​13732: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.

  • #​13859: Clarify the error message for pytest.raises() when a regex match fails.

  • #​13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".

Removals and backward incompatible breaking changes

  • #​12083: Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/.

    The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

    1. pytest a/b a/ or pytest a/ a/b are equivalent to pytest a; if an argument overlaps another arguments, only the prefix remains.
    2. pytest x.py x.py is equivalent to pytest x.py; previously such an invocation was taken as an explicit request to run the tests from the file twice.

    If you rely on these behaviors, consider using --keep-duplicates <duplicate-paths>, which retains its existing behavior (including the bug).

  • #​13719: Support for Python 3.9 is dropped following its end of life.

  • #​13766: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD_NUMBER was defined;
    now, CI mode is only activated if at least one of those variables is defined and set to a non-empty value.

  • #​13779: PytestRemovedIn9Warning deprecation warnings are now errors by default.

    Following our plan to remove deprecated features with as little disruption as
    possible, all warnings of type PytestRemovedIn9Warning now generate errors
    instead of warning messages by default.

    The affected features will be effectively removed in pytest 9.1, so please consult the
    deprecations section in the docs for directions on how to update existing code.

    In the pytest 9.0.X series, it is possible to change the errors back into warnings as a
    stopgap measure by adding this to your pytest.ini file:

    [pytest]
filterwarnings =
    ignore::pytest.PytestRemovedIn9Warning

    But this will stop working when pytest 9.1 is released.

    If you have concerns about the removal of a specific feature, please add a
    comment to 13779.

Deprecations (removal in next major release)

  • #​13807: monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend> now issues a deprecation warning when the prepended path contains legacy namespace packages (those using pkg_resources.declare_namespace()).
    Users should migrate to native namespace packages (420).
    See monkeypatch-fixup-namespace-packages for details.

Bug fixes

  • #​13445: Made the type annotations of pytest.skip and friends more spec-complaint to have them work across more type checkers.

  • #​13537: Fixed a bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.

  • #​13598: Fixed possible collection confusion on Windows when short paths and symlinks are involved.

  • #​13716: Fixed a bug where a nonsensical invocation like pytest x.py[a] (a file cannot be parametrized) was silently treated as pytest x.py. This is now a usage error.

  • #​13722: Fixed a misleading assertion failure message when using pytest.approx on mappings with differing lengths.

  • #​13773: Fixed the static fixture closure calculation to properly consi

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners December 12, 2025 17:00
@renovate-bot renovate-bot requested a review from parthea December 12, 2025 17:00
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 12, 2025
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Dec 12, 2025

Summary of Changes

Hello @renovate-bot, 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 all project dependencies to their latest versions, ensuring the project benefits from new features, performance enhancements, and security improvements. Key updates include major version upgrades for Google Cloud client libraries, the pytest testing framework, and the sphinx documentation toolchain, which may require careful validation due to potential breaking changes.

Highlights

  • Google Cloud Client Library Upgrades: Updated google-auth to 2.43.0, google-cloud-compute to 1.40.0, and google-cloud-storage to 3.7.0, introducing features like mTLS enablement, API revisions, and improved streaming capabilities.
  • Pytest Major Version Update: pytest upgraded to 9.0.2, bringing experimental subtests, native TOML configuration, a new "strict mode", and terminal tab progress, alongside dropping Python 3.9 support and making PytestRemovedIn9Warning errors by default.
  • Sphinx Documentation Toolchain Modernization: sphinx and its sphinxcontrib-* extensions received major version bumps (e.g., sphinx to 9.0.4), indicating significant enhancements and potential changes in documentation generation.
  • Minor Dependency Updates: python-dotenv updated to 1.2.1.
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[bot]
gemini-code-assist bot reviewed Dec 12, 2025
View reviewed changes
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several dependencies, including major version bumps for pytest (7.x to 9.x) and sphinx (4.x to 9.x). While keeping dependencies up-to-date is great, these major upgrades introduce breaking changes that need to be addressed.

My review includes critical feedback on the pytest upgrade, which will break the CI for the samples due to dropped support for older Python versions. I've also pointed out issues related to the sphinx upgrade, including an outdated comment and the use of a deprecated package (recommonmark) that will likely cause the documentation build to fail. Please address these points to ensure the project remains stable.

samples/cloud-client/snippets/requirements.txt
google-cloud-compute==1.40.0
google-cloud-storage==3.7.0
google-auth==2.43.0
pytest==9.0.2
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

Upgrading pytest to version 9.x will cause the CI to fail for this sample. pytest 9.x requires Python 3.10+, but the unit session in samples/cloud-client/snippets/noxfile.py is configured to run on Python versions 3.7, 3.8, and 3.9.

To fix this, you need to update samples/cloud-client/snippets/noxfile.py to remove the unsupported Python versions from the unit session decorator.

docs/requirements-docs.txt Outdated
sphinxcontrib-htmlhelp==2.1.0
sphinxcontrib-qthelp==2.0.0
sphinxcontrib-serializinghtml==2.0.0
sphinx==9.0.4
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The recommonmark package (listed on line 17) is deprecated, archived, and is likely incompatible with Sphinx 9.x. This will probably cause the documentation build to fail. It is highly recommended to migrate to myst-parser.

docs/requirements-docs.txt Outdated
Comment on lines 10 to 15
sphinxcontrib-applehelp==2.0.0
sphinxcontrib-devhelp==2.0.0
sphinxcontrib-htmlhelp==2.1.0
sphinxcontrib-qthelp==2.0.0
sphinxcontrib-serializinghtml==2.0.0
sphinx==9.0.4
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

With the upgrade to Sphinx 9.x, the comment on lines 7-9 referring to Sphinx 4.x is now outdated and should be removed to avoid confusion.

@yoshi-kokoro yoshi-kokoro removed kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Dec 12, 2025
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 12, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 12, 2025
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 15, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 15, 2025
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 15, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 15, 2025
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 17, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 17, 2025
@parthea parthea closed this Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@parthea parthea Awaiting requested review from parthea parthea is a code owner automatically assigned from googleapis/python-samples-owners

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@renovate-bot @parthea @yoshi-kokoro