Repository navigation
ci: consolidate preparation and publication in one release workflow - #74
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.
Remove the separate Prepare HMath release workflow and put preparation, full validation, artifact creation and publication directly in Publish HMath release. Users run Publish once; there is no separate preparation action or run-ID input.
.github/workflows/prepare-release.ymland move its existing jobs intopublish-python.yml.No mathematical implementation, bindings, tests, tools, documentation, README or version metadata changes. The Cabal change removes only the obsolete CI file path.
Validation: actionlint; eight workflow selection/gating scenarios; all 28 existing candidate/publication tests;
cabal check(only the existing no-maintainer warning). No release was published.Publication now targets PyPI and GitHub releases only. Hackage upload, uploader-token gating and Hackage remote checks are removed from the publishing path; the Haskell source archive remains a GitHub release asset. Python-only preflight checks for absent/matching artifacts and network failures also passed.