fix: support PEP 621 pyproject dependency scanning#2242
fix: support PEP 621 pyproject dependency scanning#2242DhineshPonnarasan wants to merge 3 commits into
Conversation
🤖 AI Agent: breaking-change-detector — API CompatibilityAPI CompatibilityNo breaking changes detected. |
|
🟡 Contributor Check: MEDIUM
Automated check by AGT Contributor Check. |
🤖 AI Agent: docs-sync-checker — Docs SyncDocs Sync
|
🤖 AI Agent: code-reviewer — View detailsTL;DR: 0 blockers, 1 warning. Solid implementation with minor follow-up needed.
Action items: None, as no blockers were identified. Warnings:
|
🤖 AI Agent: test-generator — `scripts/check_dependency_confusion.py`
|
🤖 AI Agent: contributor-guide — View detailsHi @first-time-contributor, welcome to the project and thank you for your detailed PR! 🎉 Great job adding comprehensive regression tests to cover various scenarios—this is very thorough and well-documented. Before merging, could you:
For guidance, check out CONTRIBUTING.md. Let us know if you need help! 🚀 |
🤖 AI Agent: security-scanner — View detailsNo security issues found. |
PR Review Summary
Verdict: |
Signed-off-by: Dhinesh Ponnarasan <[email protected]>
8d5145b to
766272f
Compare
Signed-off-by: Dhinesh Ponnarasan <[email protected]>
Head branch was pushed to by a user without write access
|
@imran-siddique Could you please review and approve this PR? I fixed the DCO, spell-check, and dependency-scan CI issues. |
Summary
Fixes #2206 by updating pyproject dependency confusion scanning to support standard PEP 621 layout.
Root cause:
The scanner was looking for a non-standard section shape and could miss dependencies declared under the standard project table.
What this PR changes:
Why this matters
Validation
Scope and compatibility
@imran-siddique please review when available? It fixes issue #2206 for PEP 621 pyproject scanning.