Repository navigation
Make implemented algorithms ready for PyPI publication - #46
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.
Generated algorithms are installable but currently have no publication workflow or installed-distribution gate. Add PyPI metadata questions, an explicit Trusted Publishing workflow, a release guide and changelog, and one shared build/install script used by generated CI and publishing. Publication requires a matching tag on main, a committed lockfile, completed profiles and passing validation.
The wheel now includes portable run defaults and MEDS-DEV YAMLs from their existing source files. The runner falls back to those installed defaults outside a checkout while preserving local and explicit configuration. PyPI distribution names can differ from import and CLI names. Dataset/run directories are excluded from source distributions.
The docs site renders the generated release guide directly, documents each new test, and the implementation prompt requests packaging validation. No runtime dependency or core API changes, and no automatic publication on merge.
Validation: 90 Python tests, 7 JavaScript tests, Ruff, strict MkDocs, generator distribution checks, and installed-wheel smoke checks. New tests build and install single-profile and multi-profile algorithms from their source archives and exercise CLI discovery and dry-run outside the checkout, plus release-gate failures.