CI pipelines for Docker, testing, releases - #200
Merged
Conversation
There's no good way to cache data, so limit test runs to prevent rate limiting failures
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.
The reason for all the test failures was that the old
fighshare.com/ndownloaderlinks didn't work in non-interactive sessions, though they still work from a browser. Replaced withndownloader.figshare.com.This was blocking #194, I will work on that next.
Added a release workflow that upon creation of a Github release, will
It is still necessary to manually bump pyproject.toml after release, or before and after if not doing a patch release, same as for ANTsPy.