chore(deps): require giskard-checks>=1.0.2b6 in direct dependents - #2710
Merged
Conversation
giskard-checks 1.0.2b6 is released on PyPI. Raise the lower bound in giskard-scan and in the root umbrella package, including the regorus and all-checks extras, so PyPI consumers resolve a checks lib that contains the JSONPath list/scalar fixes, the ERROR-on-unevaluable outcome change and the readability extra fix. The root bump covers the base dependency, so it applies to every "pip install giskard", not only opt-in extras. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
giskard-checks1.0.2b6was released via run 31070416694 (success, pushed to PyPI, taggedgiskard-checks/v1.0.2b6).Direct dependents still declared stale lower bounds, so a PyPI consumer could resolve an old
giskard-checksmissing a substantial batch of fixes, including:fix(checks): structural unevaluable outcomes return ERROR (not silent-green)(fix(checks): structural unevaluable outcomes return ERROR (Not silent-green) #2693)fix(checks): dot-wildcard/multi-field JSONPath returns scalar vs list depending on match count(fix(checks): dot-wildcard/multi-field JSONPath returns scalar vs list depending on match count #2605)fix(checks): descendants JSONPath always returns a list(fix(checks): descendants JSONPath always returns a list #2644)fix(checks): include readability in the all extra(fix(checks): include readability in the all extra #2705)fix(checks): skip regorus extra on platforms without a wheel(fix(checks): skip regorus extra on platforms without a wheel (Windows, linux/aarch64) #2646)Change
libs/giskard-scan/pyproject.toml>=1.0.2b3,<2>=1.0.2b6,<2pyproject.toml>=1.0.2b4,<2>=1.0.2b6,<2pyproject.tomlregorusextra>=1.0.2b4,<2>=1.0.2b6,<2pyproject.tomlall-checksextra>=1.0.2b4,<2>=1.0.2b6,<2Note that
giskard-checksis the root umbrella's base dependency, so this bump applies to everypip install giskard, not only opt-in extras. That matters here because #2705 (readability in theallextra) and #2646 (regorus platform markers) change what actually gets installed.Verification
uv lock --check— lockfile already consistent, no lock changes neededbasedpyright --level errorongiskard-checks— 0 errorsruff check libs/— passesRemaining in the release chain
giskard-scanis the last lib still unreleased. Once it ships, the root umbrella'sscan/garak/deepteamextras (currently>=1.0.0b2) will need the same treatment.🤖 Generated with Claude Code