fix(test): update typing_extensions fixture from 4.1.1 to 4.16.0 - #578
Merged
ruromero merged 1 commit intoSep 1, 2026
Merged
Conversation
Contributor
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates all Python provider pip fixtures and expected SBOM outputs from typing_extensions 4.1.1 to 4.16.0, keeping declared, installed, dependency-tree, and generated test data consistent and preventing the pipdeptree version-mismatch failure. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
The host Python environment has typing_extensions 4.16.0 installed.
The MATCH_MANIFEST_VERSIONS check (default true) aborted the pipdeptree
provider test because requirements.txt still pinned 4.1.1.
Updated all affected pip test fixtures to reflect the installed version:
- pip_requirements_txt_{no_,}ignore/requirements.txt
- pip_requirements_txt_{no_,}ignore/expected_{stack,component}_sbom.json
- pip-freeze-all.txt, pip-show.txt, pipdeptree.json
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
ruromero
force-pushed
the
fix/python-typing-extensions-version
branch
from
September 1, 2026 13:40
159f152 to
1eeae38
Compare
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #578 +/- ##
=======================================
Coverage ? 69.34%
Complexity ? 1040
=======================================
Files ? 66
Lines ? 4371
Branches ? 774
=======================================
Hits ? 3031
Misses ? 993
Partials ? 347
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
2 tasks
ruromero
added a commit
that referenced
this pull request
Sep 1, 2026
## Summary - Updates `urllib3` fixture from `1.26.16` to `2.7.0` across all pip test resources (requirements.txt, expected SBOMs, pip-freeze-all.txt, pip-show.txt, pipdeptree.json) - Sets `@SetSystemProperty(key = PROP_MATCH_MANIFEST_VERSIONS, value = "false")` on `test_the_provideStack_with_pipdeptree` so the test is no longer sensitive to version drift between the fixture pins and the actual system Python environment ## Why Follow-up to #578. The pipdeptree test calls `provideStack()` before the pipdeptree mock is wired up, causing the real `pipdeptree` binary to run and compare installed versions against the fixture `requirements.txt`. With `MATCH_MANIFEST_VERSIONS=true` (default), any drift aborts the test before assertions run. The intent of this test is to verify pipdeptree *output parsing*, not version matching — version matching is already covered by the non-pipdeptree test variants. ## Test plan - [ ] `test_the_provideStack_with_pipdeptree` passes regardless of locally installed Python package versions - [ ] Full IT suite shows 0 errors for Python provider tests 🤖 Generated with [Claude Code](https://claude.com/claude-code) ## Summary by Sourcery Make pipdeptree parsing tests deterministic across Python environments. Bug Fixes: - Stabilize the pipdeptree provider test by ensuring mocked output is configured before stack generation, preventing unintended execution of the real pipdeptree binary. Tests: - Update Python provider test fixtures to use urllib3 2.7.0 consistently across requirements, dependency snapshots, and expected SBOMs. - Disable manifest-version matching for the pipdeptree parsing test so results are independent of the host Python environment. Co-authored-by: Claude Sonnet 4.6 (1M context) <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
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.
Summary
typing_extensionsfrom4.1.1to4.16.0across Python provider test fixturesPython_Provider_Test.test_the_provideStack_with_pipdeptreewhich aborted with a version mismatch whenpipdeptreereported the actually-installed version (4.16.0) against the stale fixture pinFiles changed
pip_requirements_txt_no_ignore/requirements.txtandpip_requirements_txt_ignore/requirements.txt— manifest pins updatedexpected_stack_sbom.jsonandexpected_component_sbom.jsonin each fixture set — expected output updatedpip-freeze-all.txt,pip-show.txt,pipdeptree.json— freeze/show/pipdeptree fixtures updated for consistency with the non-pipdeptree test pathTest plan
mvn test -pl . -Dtest=Python_Provider_Test#test_the_provideStack_with_pipdeptreepassesmvn verify) shows 0 errors for Python provider tests🤖 Generated with Claude Code
Summary by Sourcery
Update Python provider test fixtures to use typing_extensions 4.16.0 and restore consistent dependency validation.
Bug Fixes:
Tests: