# No release for SARS-CoV-2 May update of nextclade\_data? **URL:** \ **Category:** Help and Getting Started\ **Created:** [June 6, 2023, 12:05am UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396 "2023-06-06T00:05:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mike\_honey](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/mike_honey/32/395_2.png) [@mike\_honey](https://nextstrain.discourse.group/u/mike_honey)\ **Post date:** [June 6, 2023, 12:05am UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/1 "2023-06-06T00:05:59Z")
I’ve been watching the releases page for the nextclade\_data repo: > **[Releases · nextstrain/nextclade\_data](https://github.com/nextstrain/nextclade_data/releases)** > > Datasets for https://github.com/nextstrain/nextclade - nextstrain/nextclade\_data So I missed that there was an update on 2022-05-10: > Going forward, should I be watching the CHANGELOG file, or perhaps this was an oversight? ---
**Author:** ![ivan-aksamentov](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/ivan-aksamentov/32/80_2.png) [@ivan-aksamentov](https://nextstrain.discourse.group/u/ivan-aksamentov)\ **Post date:** [June 8, 2023, 5:59pm UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/2 "2023-06-08T17:59:34Z")
HI Mike @mike_honey! Yes, it was an omission. It was a rare time when I released the datasets and not Cornelius. It unfortunately is not automated and I forgot to make an entry on GitHub Releases. I created the release just now. A couple of things which can help you to keep the data updated: - If you are using Nextclade Web and have a stale tab opened by the time a dataset is released, you should receive a notification in the browser (it’s a recent addition). Also, the dataset description contains the date when it was released and a link to the changelog. - If you are using Nextclade CLI, we recommend to download dataset(s) fresh once in a while, let’s say daily. This way it’s always fresh. We should probably also automate creation of GitHub Releases in the data repo ([Automate creation of GitHub releases · Issue #77 · nextstrain/nextclade\_data · GitHub](https://github.com/nextstrain/nextclade_data/issues/77)). ---
**Author:** ![mike\_honey](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/mike_honey/32/395_2.png) [@mike\_honey](https://nextstrain.discourse.group/u/mike_honey)\ **Post date:** [June 8, 2023, 10:43pm UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/3 "2023-06-08T22:43:57Z")
Hi Ivan, No worries, thanks for confirming, and for those tips. Is this month’s release far away? I’m thinking I might wait for that one, if it is on a similar schedule. Thanks Mike ---
**Author:** ![ivan-aksamentov](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/ivan-aksamentov/32/80_2.png) [@ivan-aksamentov](https://nextstrain.discourse.group/u/ivan-aksamentov)\ **Post date:** [June 10, 2023, 2:38pm UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/4 "2023-06-10T14:38:01Z")
@mike_honey I am not aware of any particular schedule. I think Cornelius just releases it when there are new clades or lineages. ---
**Author:** ![corneliusroemer](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/corneliusroemer/32/175_2.png) [@corneliusroemer](https://nextstrain.discourse.group/u/corneliusroemer)\ **Post date:** [June 13, 2023, 11:46am UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/5 "2023-06-13T11:46:49Z")
My bad, sorry, I forgot to make the gh release. I’m working on a new release, should happen this week. By the way, if you want to be on the edge, you can always use this reference tree which is built daily: [auspice](https://nextstrain.org/staging/nextclade/sars-cov-2/21L) It’s less carefully checked for correct topology and sometimes some mutations are missing in some sequences but it contains the very latest designations. You can download the tree JSON via e.g. [https://nextstrain.org/charon/getDataset?prefix=staging/nextclade/sars-cov-2/21L](https://nextstrain.org/charon/getDataset?prefix=staging/nextclade/sars-cov-2/21L) and then pass the json to nextclade cli: ```auto nextclade run -d sars-cov-2 --input-tree nightly_tree.json --output-tsv output.tsv input_sequences.fasta ``` This way you overwrite the latest release dataset tree with the nightly build. ---
**Author:** ![mike\_honey](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/mike_honey/32/395_2.png) [@mike\_honey](https://nextstrain.discourse.group/u/mike_honey)\ **Post date:** [June 18, 2023, 1:42am UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/6 "2023-06-18T01:42:33Z")
It looks like the same scenario has occurred this month - CHANGELOG.md updated without a release? ---
**Author:** ![corneliusroemer](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/corneliusroemer/32/175_2.png) [@corneliusroemer](https://nextstrain.discourse.group/u/corneliusroemer)\ **Post date:** [June 19, 2023, 1:41pm UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/7 "2023-06-19T13:41:47Z")
> It looks like the same scenario has occurred this month - CHANGELOG.md updated without a release? @mike_honey not quite 🙂 I prepared a dataset, and published it to master, but hadn’t yet released to the release _branch_, so [clades.nextstrain.org](http://clades.nextstrain.org) was still using the old dataset, only [master.clades.nextstrain.org](http://master.clades.nextstrain.org) showed the new one (this is a common development practice, master contains all changes and can be updated daily or more, and releases are done periodically) I’ve just released the dataset (put it on release branch) and this time I didn’t forget to also create a Github release, which is really nothing but a separate announcement. The github release has no implications other than to show on Github. It doesn’t impact which datasets are used by Nextclade. I hope that makes sense. ---
**Author:** ![mike\_honey](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/mike_honey/32/395_2.png) [@mike\_honey](https://nextstrain.discourse.group/u/mike_honey)\ **Post date:** [June 21, 2023, 2:54am UTC](https://nextstrain.discourse.group/t/no-release-for-sars-cov-2-may-update-of-nextclade-data/1396/8 "2023-06-21T02:54:10Z")
Sure - thanks for clarifying. For my purposes (nexclade dataset for CLI) it looks like I should watch CHANGELOG.md.