Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version nextclade binary for transition, i.e. nextclade -> nextclade2 #1089

Merged
merged 2 commits into from
Jan 10, 2024

Conversation

corneliusroemer
Copy link
Member

@corneliusroemer corneliusroemer commented Dec 14, 2023

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 nextclade2 should be used.

This binary is in both the nextstrain-base docker image and in the conda-base managed conda environment.

Users who don't use either will have to add nextclade2 to the path.

Over the next few weeks, we will transition repos to use nextclade3. The reason to add nextclade2 now is so that workflows don't break if they haven't yet transitioned to nextclade3 at the time of v3 release. It also makes it easy to search which workflows need to be changed.

Testing

  • CI

Release checklist

  • Update docs/src/reference/change_log.md in this pull request to document these changes and the new version number.

@rneher rneher merged commit bbf3c41 into master Jan 10, 2024
13 checks passed
@rneher rneher deleted the nextclade2 branch January 10, 2024 15:36
corneliusroemer added a commit that referenced this pull request Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants