chore: pin downstream packages to giskard-checks 1.0.3 - #2804
Merged
Conversation
The 1.0.3 release bump left root extras and giskard-scan on >=1.0.2, so check-extra-pins failed on main. Align lower bounds with the workspace member version. Co-authored-by: Kevin Messiaen <kevinmessiaen@users.noreply.github.com>
The extra-pins check is meant to stay strict. After uv version, rewrite matching >= pins in the root extras and downstream libs, verify them, and include those pyproject files in the release commit so the next tag cannot leave main red. Co-authored-by: Kevin Messiaen <kevinmessiaen@users.noreply.github.com>
check-extra-pins still only audits the root file for everyday CI. After a version bump, Verify now runs check-workspace-pins so every versioned PEP 508 requirement naming PACKAGE (root + libs/*) has a single >= bound equal to VERSION, catching stale giskard-scan pins the root-only check would miss. Co-authored-by: Kevin Messiaen <kevinmessiaen@users.noreply.github.com>
kevinmessiaen
changed the title
make check / check-notices failed on PR CI because licensecheck now reports boto3/botocore 1.43.81 while THIRD_PARTY_NOTICES.md still listed 1.43.80. Co-authored-by: Kevin Messiaen <kevinmessiaen@users.noreply.github.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
2 participants
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.
Description
The
giskard-checks1.0.3 release bump on main (b558f562e) left root extras andgiskard-scanpinned at>=1.0.2.make check/check-extra-pinsthen failed on Main CI lint.This PR aligns lower bounds with the workspace member version, matching #2799:
giskard-checks>=1.0.2,<2→giskard-checks>=1.0.3,<2in the rootgiskarddependencies / extras (regorus,all-checks)giskard-scanuv.lockis unchanged (workspace sources).Related Issue
CI lint failure on main after the automated version bump.
Type of Change
Coding agents
Autonomous agents with no human in the loop must read AUTONOMOUS.md before opening a PR.
PR title: agent-opened PRs must end the title with
🤖🤖🤖🤖(exactly four robot emojis). Do not omit — that suffix is how the expedited agent PR workflow picks up the PR.Checklist
CODE_OF_CONDUCT.mddocument.CONTRIBUTING.mdguide.uv.lockrunninguv lock(only applicable whenpyproject.tomlhas been modified)