Bump to 1.4.1rc1 #309
Merged
Bump to 1.4.1rc1 #309
Conversation
This file contains 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
|
@forsyth2, you created a branch with the same name as the eventual tag here, which is a totally logical thing to do. Unfortunately, it really confuses things once you do create the tag. I think that's why we're getting a different sha256 hash on conda-forge every time it tries to build from the tag. Could you delete the branch? And in the future it is probably best to either put the branch of the same name on your fork instead of the main repo or give it a different name from the eventual tag to avoid trouble. |
|
Ah, I deleted the branch locally to make the GitHub tag, but I didn't delete the branch on GitHub. |
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.
Bump to 1.4.1rc1