Push a point release to react to ref-seqs changes #255
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
I have looked at the ref-seqs release that came out a little more than a week ago 216 and I don't see any mention of one file. I am not sure why the change took place. I will email the refseqs folks to make sure this is not going back to a two file system in the next release. In the mean time all the sequences that i would expect are in this one file based on the catalog. It is a small change so I am pushing this update without the full amount of testing that we would sometimes do. Thanks to @spencerlong1 and @nikolasbasler for noticing the change in issue 254.
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.
I have looked at the ref-seqs release that came out a little more than a week ago 216, and I don't see any mention of one file. I am not sure why the change took place. I will email the refseqs folks to make sure this is not going back to a two file system in the next release. In the meantime, all the sequences that i would expect are in this one file based on the catalog.
It is a small change, so I am pushing this update without the full amount of testing that we would sometimes do.
Thanks to @spencerlong1 and @nikolasbasler for noticing the change in issue #254.