ci: separate source and built artifact validation#142
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughChangesRelease validation split
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant Developer
participant Makefile
participant publish_pypi.py
participant ArtifactValidators
Developer->>Makefile: make validate-gate2
Makefile->>publish_pypi.py: run --dry-run
publish_pypi.py-->>Makefile: source contract result
Developer->>Makefile: make validate-built-artifacts
Makefile->>ArtifactValidators: validate complete present artifacts
ArtifactValidators-->>Makefile: validation result
🚥 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 |
|
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
Separate source and structural release validation from final built-artifact verification.
This fixes Gate 2 behavior where ignored historical files under
releases/could incorrectly trigger final PyPI artifact validation.
Root cause
validate-gate2previously treated the presence of either an artifact or itschecksum sidecar as a trigger for final artifact validation.
The ignored historical
releases/0.2.3/tree contains PyPI artifacts but keepsolder checksum evidence under
.checksums/. This caused Gate 2 to invoke thefail-closed final PyPI validator and require adjacent checksum sidecars.
The defect was in Gate 2 dispatch logic, not in:
scripts/verify_artifact.pyscripts/verify_release_assets.pyWhat changed
Added:
This runs:
The default:
now performs source and structural validation only:
Final built-artifact verification is now explicit:
Fail-closed artifact behavior
For each optional artifact:
For the PyPI artifact set:
validate-pypi-contract;Required PyPI files:
.sha256.sha256Preserved contracts
This PR does not change:
scripts/verify_release_assets.py;.github/workflows/release.yml;No
.checksums/fallback was added.Tests
Added focused coverage for:
Validation
Passed:
Observed:
Scope
Changed only:
Makefiledocs/release/release-process.mdtests/packaging/test_release_asset_count_gate.pyNo release artifacts were created or modified.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation