6.0.0
These release notes are automatically extracted from the full changelog.
This release contains a potentially-breaking change for existing usages of nextstrain view, though we expect the change to impact very few usages. The change is described below.
Improvements
-
nextstrain viewnow supports viewing narratives, as was always intended. Previously the launched Auspice would either show baked in test narratives or no narratives at all, depending on the Auspice version in the runtime. (#240) -
nextstrain viewnow supports being given more kinds of paths, including paths to a specific dataset or narrative file and paths to directories containing auspice/ and/or narratives/ subdirectories.This is a potentially-breaking change, as
nextstrain view <dir>will now prefer to show datasets from<dir>/auspice/ if that subdirectory exists. Previously it would only ever look for datasets in the given<dir>. We expect this to change behaviour for very few usages as it only affects situations where<dir>contains both datasets and an auspice/ directory.See
nextstrain view --helpfor more details on the kinds of paths supported. (#240) -
nextstrain viewnow automatically opens Auspice in a new browser tab (or window) by default when possible.If a specific dataset or narrative file was given as the path to
nextstrain view, then that dataset or narrative is opened. Otherwise, if there's only a single dataset or narrative available in the directory path given tonextstrain view, then it is opened. Otherwise, Auspice's listing of available datasets and narratives is opened. (#240)
-
Local images used in a narrative are now automatically embedded into it when uploading the narrative to nextstrain.org via
nextstrain remote upload. In local text editors which can render Markdown, this permits previewing of narratives that reference images on the local filesystem without requiring manual conversion to remote images or embedded images before upload. (#235) -
The
nextstrain remote uploadcommand now outputs a nicer error message that's more interpretable and actionable when nextstrain.org returns a "bad request" error. The error message also includes the error details returned by nextstrain.org. (#238)
Development
- The Conda runtime now uses Micromamba 1.0.0 (an upgrade from 0.27.0). (#233)