Repository navigation
chore(deps): bump hypothesis from 6.168.5 to 6.169.1 - #79
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [hypothesis](https://github.com/HypothesisWorks/hypothesis) from 6.168.5 to 6.169.1. - [Release notes](https://github.com/HypothesisWorks/hypothesis/releases) - [Commits](HypothesisWorks/hypothesis@v6.168.5...v6.169.1) --- updated-dependencies: - dependency-name: hypothesis dependency-version: 6.169.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
## Scope One rollup for the four open Dependabot PRs (#78 aiohttp 3.14.4, #79 hypothesis 6.169.1, #80 ty 0.0.87, #81 github-actions group). No eMudhra-related pin changes are needed here (this repository's locks carry no stale certifi). No unrelated fixes. - Workflow files (ci/benchmark/release) are byte-identical to #81; both action pins were verified against official tag APIs (setup-uv v10.3.0, mise-action v5.1.2). - `pyproject.toml` is byte-identical to #80 (ty 0.0.87 in the lint group; ty is already exempt from this repo's 7-day cooldown by its own policy). - The lock was re-resolved natively with the CI-pinned uv **0.11.17** and targeted upgrades. Result exactly matches the union of the three lock bots plus one constraint-forced transitive: aiohttp **3.14.4** (requires `yarl>=1.25.1`, matching #78's own lock), hypothesis **6.169.1**, ty **0.0.87**, yarl **1.25.1**. Package set unchanged (56 records, none added/removed). - `packages/tablecodec-docling/uv.lock` gained one mechanical line: bot #80's root `ty` specifier change is embedded in the bridge lock's local-package metadata (`requires-dev`), and the first CI run failed the `docling bridge` job on exactly that drift. Verified at base (check passes) vs this head (fails) before the one-line regeneration; after it, `uv lock --check` (uv 0.11.17) and `just docling-ci` (30 tests) pass locally. Package set unchanged (41 records). - Full re-resolution regenerated two transitive dependency-marker lines (`anyio`, `httpcore2` gain `sys_platform != 'emscripten'` exclusions) — an artifact of the pinned uv's current resolver; versions and artifacts are unchanged, and the repo's own `uv lock --check` accepts the result. ## Verification - PASS: uv 0.11.17 `uv lock --check` and CI-parity `uv sync --locked --group lint --extra dev --extra cli --extra teds`. - PASS: `just ci` on the final tree — ruff lint/format, ty, pytest **349 passed** (2 benchmark deselected by design), semgrep (0 findings), rule fixtures 3/3, docs-check regenerated tables identical. (An earlier local failure was an invocation mismatch — dev/cli are extras, not groups; no repo change was needed.) - PASS: independent Codex static review for PR publication (not merge approval) covered the original five-file diff — no deployment on main push (benchmarks only), release tag-only, zero-dependency core and cooldown policy intact, lock contains exactly the intended versions; the sixth file (bridge lock metadata line) is a mechanical consequence proven by the base-vs-head check above. ## Merge boundary All related checks on the final head must succeed. Recheck base/head and all workflow paths, then use a SHA-matched squash merge only if no main-triggered deployment risk exists (`benchmark.yaml` runs benchmarks on main push; `release.yaml` is `v*`-tag-only). No tag/release/publish is authorized. Close #78–#81 only after merged main is verified to contain their changes.
|
Included in reviewed rollup #82. All ruleset-required final-head checks passed (8 test matrix legs, pytest-benchmark, semgrep, pip install -e ., plus docling bridge after the bridge-lock metadata line was regenerated). Merged main was verified tree-identical to the tested head. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps hypothesis from 6.168.5 to 6.169.1.
Commits
b943753Bump hypothesis version to 6.169.1 and update changeloge8d38beMerge pull request #4892 from MarcoGorelli/data-strategy-keyword-argsb3cfe2aMerge pull request #4901 from Liam-DeVoe/redistribute-numeric-pairs-int-testda4f5d0claude: Test redistributing from a float into a large integer82fa40aBump hypothesis version to 6.169.0 and update changelog0116655Merge pull request #4899 from Arjun-Aravind/fix/uv-download-metadata-url4f7ef96claude: exclude rarely-hit realize branch from coverage4d42db9Update uv download-metadata URL1484f6dMerge pull request #4896 from Liam-DeVoe/drop-python-3.10e3e5feaclaude: address review commentsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)