search

googleapis / doc-pipeline

Apache License 2.0
10 stars 11 forks source link

chore(deps): update dependency pluggy to v1.3.0 #534

Closed renovate-bot closed 1 year ago

renovate-bot commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pluggy ==1.2.0 -> ==1.3.0 age adoption passing confidence

Release Notes

pytest-dev/pluggy (pluggy) ### [`v1.3.0`](https://togithub.com/pytest-dev/pluggy/blob/HEAD/CHANGELOG.rst#pluggy-130-2023-08-26) [Compare Source](https://togithub.com/pytest-dev/pluggy/compare/1.2.0...1.3.0) \========================= ## Deprecations and Removals - `#​426 `\_: Python 3.7 is no longer supported. ## Features - `#​428 `\_: Pluggy now exposes its typings to static type checkers. As part of this, the following changes are made: - Renamed `_Result` to `Result`, and exported as :class:`pluggy.Result`. - Renamed `_HookRelay` to `HookRelay`, and exported as :class:`pluggy.HookRelay`. - Renamed `_HookCaller` to `HookCaller`, and exported as :class:`pluggy.HookCaller`. - Exported `HookImpl` as :class:`pluggy.HookImpl`. - Renamed `_HookImplOpts` to `HookimplOpts`, and exported as :class:`pluggy.HookimplOpts`. - Renamed `_HookSpecOpts` to `HookspecOpts`, and exported as :class:`pluggy.HookspecOpts`. - Some fields and classes are marked `Final` and `@final`. - The :ref:`api-reference` is updated to clearly delineate pluggy's public API. Compatibility aliases are put in place for the renamed types. We do not plan to remove the aliases, but we strongly recommend to only import from `pluggy.*` to ensure future compatibility. Please note that pluggy is currently unable to provide strong typing for hook calls, e.g. `pm.hook.my_hook(...)`, nor to statically check that a hook implementation matches the hook specification's type.

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 has been generated by Mend Renovate. View repository job log here.

forking-renovate[bot] commented 1 year ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

âš  Warning: custom changes will be lost.