Repository navigation
Build the conda package from the PyPI release - #8
Closed
chengbiao-jin wants to merge 1 commit into
Closed
chengbiao-jin wants to merge 1 commit into
chengbiao-jin wants to merge 1 commit into
Conversation
- Use the source package published on PyPI, so conda and PyPI ship the same files - Fail with a clear message when the version isn't on PyPI - Fail when the recipe version doesn't match the tag
Collaborator
Author
|
Folded into #7. |
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.
Release workflow only — no source changes.
The release order is unchanged: tag, then PyPI, then approve the conda job. A forgotten PyPI upload now stops the conda job instead of passing unnoticed.
Verification
Ran the new step locally: against 1.0.4 it points the recipe at the PyPI file with PyPI's checksum, which matches the uploaded package. An unpublished version and a tag that doesn't match the recipe both exit with an error. Not run in Actions yet; the first real run is the next release tag.