Version nextclade binary for transition, i.e. nextclade -> nextclade2#1089
Merged
Version nextclade binary for transition, i.e. nextclade -> nextclade2#1089
nextclade -> nextclade2#1089Conversation
corneliusroemer
added a commit
that referenced
this pull request
Jan 16, 2024
This was erroneously omitted by me in #1089
4 tasks
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
2 participants
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.
Description of proposed changes
Soon we will release nextclade v3. Once nextclade v3 hits bioconda, workflows that rely on v2 syntax will break. To prevent this, this PR makes it explicit that the syntax used is for v2 and that the v2 binary
nextclade2should be used.This binary is in both the
nextstrain-basedocker image and in theconda-basemanaged conda environment.Users who don't use either will have to add
nextclade2to the path.Over the next few weeks, we will transition repos to use
nextclade3. The reason to addnextclade2now is so that workflows don't break if they haven't yet transitioned tonextclade3at the time of v3 release. It also makes it easy to search which workflows need to be changed.Testing
Release checklist
docs/src/reference/change_log.mdin this pull request to document these changes and the new version number.