Skip to content

chore(deps): bump xmlschema, bandit, diff-cover and ruff - #220

Merged
sebastienrousseau merged 1 commit into
mainfrom
chores/dev-deps
Aug 13, 2026
Merged

chore(deps): bump xmlschema, bandit, diff-cover and ruff#220
sebastienrousseau merged 1 commit into
mainfrom
chores/dev-deps

Conversation

@sebastienrousseau

Copy link
Copy Markdown
Owner

Consolidates #210, #212, #213 and #215.

Why they could not go in individually

Each rewrites poetry.lock. Merging any one made the other three conflict, and the next merge invalidated the one after it — the queue never converged. They are applied here as one manifest change and one lock regeneration.

package from to
xmlschema >=3.4.0,<4.0.0 >=4.3.2,<5.0.0
bandit ^1.7.0 ^1.9.4
diff-cover ^8.0.0 ^10.5.0
ruff ^0.15.0 ^0.16.2 → resolves 0.16.3

The two that deserved more than a green tick

xmlschema 3 → 4 is a major bump, and this project validates ISO 20022 messages against XSDs — the one thing it must not get wrong. Beyond the suite passing, 6 of the 34 bundled schemas were loaded directly under 4.3.2, and the xml- and validate-tagged tests were run as their own groups (140 and 177 passed).

ruff 0.15 → 0.16 can introduce new lint rules that fire on existing code. Both ruff check and ruff format --check were run at the exact resolved version, not an approximation.

Verification

gate result
pytest 1468 passed, 9 skipped
ruff check . exit 0
ruff format --check . 223 files already formatted
poetry check --lock exit 0

Authorship

These could not be cherry-picked — every one conflicts on the lock — so the manifest edits were reapplied by hand. Credit for the bumps belongs to Dependabot (#210, #212, #213, #215), which is why those are referenced rather than silently closed.

Consolidates four Dependabot pull requests that could not be merged
individually. Each rewrites poetry.lock, so merging any one of them made
the other three conflict — the queue never converged. They are applied
here as one manifest change and one lock regeneration.

    xmlschema   >=3.4.0,<4.0.0  ->  >=4.3.2,<5.0.0
    bandit      ^1.7.0          ->  ^1.9.4
    diff-cover  ^8.0.0          ->  ^10.5.0
    ruff        ^0.15.0         ->  ^0.16.2   (resolves 0.16.3)

xmlschema is a major bump and this project validates ISO 20022 messages
against XSDs, so it was checked beyond the suite passing: 6 of the 34
bundled schemas were loaded directly under 4.3.2, and the xml- and
validation-tagged tests were run as their own groups.

ruff 0.15 -> 0.16 can introduce new rules; `ruff check` and
`ruff format --check` were run at the exact resolved version rather
than assumed.

    pytest                  1468 passed, 9 skipped
    ruff check .            exit 0
    ruff format --check .   223 files already formatted
    poetry check --lock     exit 0

Authorship note: these could not be cherry-picked — every one conflicts
on the lock — so the manifest edits were reapplied by hand. Credit for
the bumps belongs to Dependabot (#210, #212, #213, #215).

Signed-off-by: Sebastien Rousseau <sebastian.rousseau@gmail.com>

Assisted-by: Claude:claude-opus-4-7
@codecov

codecov Bot commented Aug 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (40cf836) to head (f78d0f6).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #220   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           79        79           
  Lines         3854      3854           
  Branches       467       467           
=========================================
  Hits          3854      3854           
Flag Coverage Δ
unittests 100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant