Repository navigation
Fix open Dependabot security alerts - #33
Merged
Merged
Conversation
Upgrade vulnerable packages in poetry.lock to at least their first patched versions, raise the pytest dev constraint to >=9.0.3,<10 so the patched release can resolve, and bump SonarSource/sonarqube-scan-action to v6.0.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Poetry 2.3.2 wrote a content hash that the Poetry 2.2 used in CI rejects. Package versions are unchanged. Co-Authored-By: Claude Opus 5.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
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.
Summary
Fixes all 77 open Dependabot alerts. Every vulnerable package in
poetry.locknow sits at or above its first patched version. No alert is left open.The lockfile was updated with
poetry update --lock <pkgs>, limited to the vulnerable packages. Poetry took the newest version each existing constraint allows, so some land above the minimum patched version.Transitive changes pulled in by the above: distlib 0.4.0 -> 0.4.4, packaging 26.0 -> 26.3, python-discovery 1.2.0 -> 1.6.4, typing-extensions 4.15.0 -> 4.16.0. autobahn 26 no longer needs py-ubjson, so it is gone from the lock. The lock was written with Poetry 2.2.1, the version CI uses; a lock written by Poetry 2.3.2 failed
poetry installin CI with a content-hash mismatch.Supersedes #32 (same sonarqube-scan-action bump).
Evidence
Local run, Windows, Python 3.13.11, after
poetry install --all-groups:poetry run pytest -v: 3 passed (pytest 9.1.1)poetry run ruff check: All checks passedpoetry run ruff format --check: 9 files already formattedpoetry checkandpoetry build: OKtransmeaspy,qcodes,quantify,zhinst.qcodes,qcodes_contrib_drivers,PIL,tornado,autobahn,matplotlib,requests,cryptography: OK (Pillow 13.0.0, tornado 6.6)The test suite is still the template
my_moduletests, so it says little about runtime behaviour with the new versions. The import smoke test is the stronger signal here.SonarCloud fails at the scan step:
GET https://api.sonarcloud.io/analysis/jresreturns HTTP 403 and the scanner asks to checkSONAR_TOKEN. Install, tests and coverage pass before that step. The token is set but is rejected, so it has probably expired or been revoked. SonarCloud has failed on main since March 2026 (last success September 2025), so this is a secrets problem that predates this PR, not something it caused. The token needs regenerating in SonarCloud and updating in the repo secrets.Merge Danger
Door: two-way
Revert the commit to restore the old lockfile.
Blast Radius: dependencies
ujson 6 and cbor2 6 are major bumps. Both are transitive (via autobahn/qcodes), not imported by TransMeasPy itself. Anyone pinning pytest <9 in a dev env will need to update.
🤖 Generated with Claude Code