build(deps): bump hypothesis from 6.156.6 to 6.165.5 - #699
build(deps): bump hypothesis from 6.156.6 to 6.165.5#699dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [hypothesis](https://github.com/HypothesisWorks/hypothesis) from 6.156.6 to 6.165.5. - [Release notes](https://github.com/HypothesisWorks/hypothesis/releases) - [Commits](HypothesisWorks/hypothesis@v6.156.6...v6.165.5) --- updated-dependencies: - dependency-name: hypothesis dependency-version: 6.165.5 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Pull request overview
OpenCode cannot approve yet because required coverage evidence did not pass.
Review outcome
1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence
-
Problem: The required coverage-evidence job result was
failure, so OpenCode cannot establish approval sufficiency for this head. -
Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.
-
Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports
successwith required evidence or explicit no-source not-applicable evidence. -
Regression test: Keep the approval branch checking
needs.coverage-evidence.result == successbefore posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present. -
Result: REQUEST_CHANGES
-
Reason: coverage-evidence result was
failure, so required test/docstring evidence was not proven for current headc5a0028bd1109086ce88d5585794ee2184d65731. -
Head SHA:
c5a0028bd1109086ce88d5585794ee2184d65731 -
Workflow run: 32131984675
-
Workflow attempt: 1
Coverage evidence
Coverage evidence job did not run or did not publish coverage evidence.
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file: requirements-property.txt"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file: requirements-property.txt"]
R1 --> V1["required checks"]
OpenCode Review Overview
Pull request overviewOpenCode cannot approve yet because required coverage evidence did not pass. Review outcome1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence
Coverage evidenceCoverage evidence job did not run or did not publish coverage evidence. Changed-File Evidence Mapflowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file: requirements-property.txt"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file: requirements-property.txt"]
R1 --> V1["required checks"]
|
|
Superseded by #754. |
Bumps hypothesis from 6.156.6 to 6.165.5.
Commits
2f49474Bump hypothesis version to 6.165.5 and update changelog15e547bMerge pull request #4850 from Liam-DeVoe/rename-internal-example-terminologyd7fcdfaMerge remote-tracking branch 'upstream/master' into plait/review-hypothesis-4850265fcc3Bump hypothesis version to 6.165.4 and update changelogebb7b7bMerge remote-tracking branch 'upstream/master' into rename-internal-example-t...6ec2e31Merge pull request #4835 from Zac-HD/claude/hypothesis-3176-design-hr97hhdecc491update a few more380ff61claude: rename remaining internal example terminology to test case0570b5bwording and tweaks459cc24Merge pull request #4845 from HypothesisWorks/create-pull-request/patchDependabot 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)