Check crate package paths instead of a fixed file count - #27
Merged
Merged
Conversation
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
1 participant
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.
The crates.io workflow rejected v2.5.4 because it required exactly 81 package files. Adding the two Standard 14 metric modules correctly produces 83 files, so the count prevented publication after the source tests had passed.
Compare the Cargo package listing with the checked-out release's tracked
src/files and the explicitly allowed root metadata/license files. Fail on missing, unexpected, or duplicate entries, and retain the existing build-output/secret-path exclusion. The workflow can then publish the existing immutable v2.5.4 tag.Validation: execute the exact Python block extracted from the workflow against the actual 83-file Cargo listing; reject a missing file, an unexpected replacement with the same count, and a duplicate. Focused packaging/release tests, the full 492-test Python suite using the built 2.5.4 runtime, and metadata checks pass. This changes release automation only.