Scan every customer-readable source distribution surface - #92
Merged
Conversation
📝 WalkthroughWalkthroughThe release updates the package to version ChangesRelease validation
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant ReleaseWorkflow
participant Build
participant SourceDistribution
participant StorefrontValidator
ReleaseWorkflow->>Build: build versioned source distribution
Build->>SourceDistribution: create exact .tar.gz archive
ReleaseWorkflow->>StorefrontValidator: validate --sdist archive
StorefrontValidator->>SourceDistribution: inspect members and metadata
StorefrontValidator-->>ReleaseWorkflow: return validation result
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/validate_storefront_claims.py`:
- Around line 414-416: Update validate_sdist to exclude members whose suffix is
in BINARY_SUFFIXES before applying the MAX_SDIST_TEXT_BYTES check, allowing
large known binaries such as .wasm files to bypass the text-size failure while
preserving the limit for text candidates. Add a regression test covering a
binary member larger than MAX_SDIST_TEXT_BYTES.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 818f2254-18f1-4c40-925a-acbafeec7f82
📒 Files selected for processing (9)
.env.example.github/workflows/publish.yml.github/workflows/test.ymlCHANGELOG.mdoilpriceapi/version.pypyproject.tomlscripts/validate_storefront_claims.pytests/test_release_readiness.pytests/test_storefront_claims.py
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
1.12.8Red-green proof
.wasmwas falsely rejected before binary classificationRelease
After protected-main merge, publish only through the existing governed
v1.12.8PyPI OIDC workflow. Then verify public wheel+sdist hashes/provenance, cold-install the exact registry wheel, run live keyless/authenticated smokes, and observe the scheduled synthetic.