fix: validate browser extra before publishing#88
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #88 +/- ##
=======================================
Coverage 93.48% 93.48%
=======================================
Files 11 11
Lines 2026 2026
Branches 265 265
=======================================
Hits 1894 1894
Misses 84 84
Partials 48 48 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughSummary by CodeRabbit
WalkthroughA new script ChangesWheel Validation Script and CI/CD Integration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary: add a release artifact validator that inspects the built wheel for the browser extra, patchright dependency, and browser transport module; run it in CI and Release before publishing; and let PyPI fail if a version already exists instead of silently skipping a stale artifact. Why: PyPI has an immutable stale peakbagger 1.10.0 wheel that lacks the documented browser extra. The source tree was fixed, but the installable artifact users get was not. Validation: ruff check, ruff format check, pytest, uv build, and scripts/validate_distribution.py all passed locally.