ci: add post-publish smoke test workflow - #66
Merged
Conversation
Triggers on tag push (v*) or manual dispatch. Installs the published package from PyPI in a clean environment and runs a smoke test: - Shield: URLAllowList safe call + blocked call - Shield: default keyword filter safe call + blocked call - Async: shielded coroutine safe + blocked - CLI: modelfuzz --version matches package version - py.typed present in installed files - sdist is clean (no stray files, py.typed and AGENTS.md present) This catches breakage that only surfaces in the published artifact — missing files, bad metadata, dependency resolution failures — that the in-repo CI can't detect because it tests the source tree directly.
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.
Triggers automatically on tag push (
v*) or manual dispatch. Installs the published package from PyPI in a clean environment and runs a smoke test against the published artifact — not the source tree.What it checks:
URLAllowListsafe call passes, blocked call raisesModelFuzzBlockErrormodelfuzz --versionmatchesmodelfuzz.__version__py.typedpresent in installed files.claude/.env/__pycache__,py.typedandAGENTS.mdpresent)This catches breakage that only surfaces in the published package — missing files, bad metadata, dependency resolution failures — that the in-repo CI can't detect because it tests the source tree directly.
Usage:
v*tag (your normal release flow) triggers itgh workflow run smoke-test.yml -f version=0.3.8or via the Actions UI