chore(deps): update osv-lib

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
grpcio	1.80.0 → 1.81.0
grpcio-tools	1.80.0 → 1.81.0
hypothesis (changelog)	6.153.2 → 6.155.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

grpc/grpc (grpcio)

v1.81.0

Compare Source

This is release 1.81.0 (graphic) of gRPC Core.

For gRPC documentation, see grpc.io. For previous releases, see Releases.

This release contains refinements, improvements, and bug fixes, with highlights listed below.

Core

• [EventEngine] Fix a potential use-after-free error on Windows. (#​42078)
• [ssl] Server side handshaker factory stores a map of key signers. (#​42002)
• [Core] Fix completion queue shutdown race on weak memory models (ARM). (#​41510)
• [EventEngine] Fix a Windows race that causes an assertion error. (#​41563)
• [grpc_error] enable error_flatten experiment in OSS. (#​41471)
• [Python] Trim Python2 backward compatiblity syntax - removed (object) inheritance. (#​41708)

Objective-C

• [ObjC] Add receiveNextMessage to GRPCUnaryProtoCall. (#​42260)

Python

• [Python] Add typing_extensions dep to aio Bazel target. (#​42001)
• [Python] [Pyright] Part 1 - Pyright for src/python/grpcio/grpc/aio/_base_server.py. (#​42240)
• [Python] Drop 3.9. (#​42145)
• [Python] grpc-status: Relax protobuf dependency upper bound to allow 7.x. (#​41948)
• [Python] [Typeguard] Part 5 - Add Typeguard SYNC Stack in tests. (#​40278)
• [Python] Remove GIL from ReceiveMessageOperation.un_c method. (#​41812)
• [Python] Support observability in AsyncIO stack. (#​41573)

Ruby

• [Ruby] Drop support for EOL Ruby 3.1 and clean up. (#​41435)
• [Ruby] Composed CallCredentials keep a reference to their source. (#​41782)

HypothesisWorks/hypothesis (hypothesis)

v6.155.1: Hypothesis version 6.155.1

Compare Source

Shrinking large floats, strings, and bytestrings is now much faster in
some cases (issue #​4006).

The canonical version of these notes (with links) is on readthedocs.

v6.155.0: Hypothesis version 6.155.0

Compare Source

"from_dtype()" now supports the variable-width string dtype
"numpy.dtypes.StringDType", generating arbitrary strings via "text()"
(issue #​4039).

Additionally, passing a dtype class such as "np.dtypes.StringDType"
where an instance like "np.dtypes.StringDType()" was expected now
raises a clear error, rather than the previous confusing message (or
silent coercion to the object dtype in "arrays()").

The canonical version of these notes (with links) is on readthedocs.

v6.154.2: Hypothesis version 6.154.2

Compare Source

This patch improves the type annotations of "fixed_dictionaries()",
which now accepts a "Mapping" rather than requiring an invariant
"dict". Because the value type is covariant, type-checkers can now
infer the generated type even when the strategies are heterogeneous,
e.g. a "mapping" annotated as "dict[str, SearchStrategy[int] |
SearchStrategy[str]]" (issue #​4665).

The "mapping" and "optional" arguments may now also have different key
and value types, which are unioned in the inferred result.

The canonical version of these notes (with links) is on readthedocs.

v6.154.1: Hypothesis version 6.154.1

Compare Source

This patch fixes a bug where resolving recursive forward references in
"from_type()" (such as "A = list[Union["A", str]]", added in
v6.152.11) could recurse until it hit the interpreter's recursion
limit before falling back to a deferred strategy. Because this
depended on the ambient stack depth, it occasionally surfaced as a
spurious "RecursionError" or other flaky failure. We now break the
cycle eagerly by deferring, so resolution uses a small and constant
amount of stack regardless of how deeply nested the reference is.

The canonical version of these notes (with links) is on readthedocs.

v6.154.0: Hypothesis version 6.154.0

Compare Source

"fixed_dictionaries()" now varies the iteration order of the dicts it
generates, rather than always placing the required keys first, to help
find bugs in code which is sensitive to key order (issue #​3906). If
you need a stable order, we recommend using
"fixed_dictionaries(...).map(stable_sort_function)" or similar.

The canonical version of these notes (with links) is on readthedocs.

v6.153.6: Hypothesis version 6.153.6

Compare Source

The "--hypothesis-show-statistics" report now accounts for the
"Phase.explain" phase separately, rather than including its runtime
and test cases in the "Phase.shrink" phase (issue #​4179).

The canonical version of these notes (with links) is on readthedocs.

v6.153.5: Hypothesis version 6.153.5

Compare Source

This patch dramatically improves the performance of "from_type()" on
hierarchies of abstract classes whose subclasses refer back to the
base class (directly, or via a sibling subclass) in their annotations.
Resolution previously took time cubic in the number of subclasses; we
now resolve each type only once (issue #​4729).

The canonical version of these notes (with links) is on readthedocs.

v6.153.4: Hypothesis version 6.153.4

Compare Source

This patch fixes a bug where fuzz_one_input did not track the
"interesting_origin" of failures (issue #​4420). As a result, it only
saved the single smallest failure to the database rather than the
smallest example of each distinct failure, and the
"interesting_origin" was missing from observability reports.

The canonical version of these notes (with links) is on readthedocs.

v6.153.3: Hypothesis version 6.153.3

Compare Source

This patch fixes a bug where "decimals()" with the "places" argument
could generate values outside the "min_value" and "max_value" bounds,
when those bounds had more fractional digits than "places" (issue
#​4651).

The canonical version of these notes (with links) is on readthedocs.

---

Configuration

📅 Schedule: (in timezone Australia/Sydney)

• Branch creation
  • "before 6am on wednesday"
• 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.

[forking-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml

Artifact update for hypothesis resolved to version 6.155.2, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 6.155.1
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/