chore(deps): Update dependency hypothesis to v6.160.0

[williaby]

Summary

Why

Scheduled patch update, bug fixes and security patches with no API changes.

Changes

This PR contains the following updates:

Package	Change	Age	Confidence
hypothesis (changelog)	==6.156.6 → ==6.160.0

---

Warning

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

Impact

• ✅ Patch update: bug fixes and security patches only
• ✅ No breaking changes

Acceptance Criteria

• All CI checks pass

Testing

• CI gates pass (tests, lint, type checking, security scan)

Notes

---

Release Notes

HypothesisWorks/hypothesis (hypothesis)

v6.160.0: Hypothesis version 6.160.0

Compare Source

"Bundle" now supports efficient ".filter()" and ".map()" methods,
which compose with "consumes()" in either order (issue #​3944).
Previously, "consumes(bundle).filter(fn)" could remove rejected values
from the bundle while retrying, and "consumes(bundle.filter(fn))" was
a type error; filtered draws now select among currently-matching
values and consume only the value which was actually drawn.

Thanks to Reagan Lee for the initial implementation of this feature in
pull request #​4084!

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

v6.159.0: Hypothesis version 6.159.0

Compare Source

Hypothesis has historically referred to the single execution of a test
function as an "example". However, we have in recent years tended to
call a single execution a "test case" instead, which we think is a
more precise and less overloaded term.

This release updates user-facing documentation, log messages, and
error messages to use the "test case" terminology. Some observability
fields which contain raw strings from Hypothesis might change in
format as a result.

This is not a breaking change, as we have intentionally not changed
any code APIs. In particular, "settings.max_examples" has not been
changed.

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

v6.158.1: Hypothesis version 6.158.1

Compare Source

This patch implements filter-rewriting for "times()" and
"datetimes()": simple comparison filters such as
".filter(partial(operator.ge, bound))" are rewritten into efficient
bounds, as "dates()" already did. This includes strategies inferred
from annotated-types bounds like "Annotated[datetime, Gt(...)]", and
contradictory filters now give an empty strategy instead of failing
health checks.

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

v6.158.0: Hypothesis version 6.158.0

Compare Source

"datetimes()" now accepts timezone-aware "min_value" and "max_value"
bounds, which are treated as moments in time. In this case "timezones"
defaults to "timezones()", and each generated datetime lies between
the two moments. Passing one aware and one naive bound is an error.

If annotated-types has been imported, the overloaded type hints for
this strategy now distinguish naive from aware datetimes using
"Timezone" metadata.

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

v6.157.2: Hypothesis version 6.157.2

Compare Source

This patch continues our migration of Hypothesis internals to rust
(issue #​4740), porting some internal float helpers. There should be no
user-visible change. If you see any change in behavior, please open an
issue.

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

v6.157.1: Hypothesis version 6.157.1

Compare Source

Internal refactoring of how "Phase.explain" tracks which parts of a
failing example can vary, with no user-visible change.

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

v6.157.0: Hypothesis version 6.157.0

Compare Source

"from_type()" now supports the annotated-types "Timezone" constraint
on "datetime" and "time", resolves the typing-extensions
"TypeAliasType" backport as well as the native form from Python 3.12+,
and suggests subscripting generic aliases like
"annotated_types.LowerCase" if they are mistakenly passed as
"Annotated" metadata.

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

v6.156.9: Hypothesis version 6.156.9

Compare Source

This release improves observability output under symbolic backends by
displaying arguments generated by "data()" as "data(...)".

Thanks to zhangli091011 for this fix!

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

v6.156.8: Hypothesis version 6.156.8

Compare Source

This patch improves the performance of unique collections drawing from
a fixed pool of elements, such as "sets()" of "sampled_from()", under
symbolic-execution backends such as hypothesis-crosshair.

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

v6.156.7: Hypothesis version 6.156.7

Compare Source

This patch fixes a bug where calling ".flatmap()" on a "consumes()"
bundle raised an error (issue #​4427).

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

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "after 10pm every weekday,before 5am every weekday,every weekend"
• 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.

---

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

---

This PR has been generated by Mend Renovate.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the development dependency hypothesis from version 6.156.6 to 6.160.0.

Changes

Development dependency update

Layer / File(s)	Summary
Update Hypothesis version requirements-dev.txt	Bumps hypothesis from 6.156.6 to 6.160.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• ByronWilliamsCPA/pp-security-master#125: Updates the same hypothesis dependency in requirements-dev.txt.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: bumping the hypothesis dependency to 6.160.0.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/hypothesis-6.x

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@requirements-dev.txt`:
- Line 100: Update the Hypothesis dependency entry in uv.lock to match version
6.157.0, then regenerate requirements-dev.txt from the refreshed lockfile so
both generated dependency sources are consistent and uv sync --frozen resolves
the newer version.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b32eb84c-d98d-47f3-bdf9-2bea3ba1e667

📥 Commits

Reviewing files that changed from the base of the PR and between 4f29d4e and 2f49b9d.

📒 Files selected for processing (1)

• requirements-dev.txt