Repository navigation
Add built-package release smoke test - #33
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
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
Add a release-engineering smoke test for the actual built package, separate from the existing editable-install and beginner-flow coverage.
Current CI already proves
pip install -e .and the full checkout-based beginner workflow. Before rc2, it should also prove that a normal sdist/wheel build contains everything required at runtime.New CI job
The
package-smokejob:python -m build;.tar.gzand one.whl;/tmpso imports cannot accidentally rely on the repository checkout;pyproject.toml;ebus-evidence --version;ebus-evidence --help;hw5103-open-evidenceprofile and checks its expected v2 check IDs.Because the default
python -m buildflow builds the wheel from the source distribution, this also catches source-distribution omissions that would prevent a valid wheel build.Scope
CI/release validation only.
No runtime, parser, Evidence, installer, profile or submission behaviour changes. No package is uploaded or published.