Closed tsibley closed 12 months ago
Test run: https://github.com/nextstrain/conda-base/actions/runs/6202996684
However, this as-is right now tests only that there exists some package version that's initially installable. It doesn't guarantee that package version is the latest. We could do that two ways:
devel/download-latest
does) and pass it into setup-nextstrain-cli
as an input, which would then pass it to nextstrain
in NEXTSTRAIN_CONDA_BASE_PACKAGE
.nextstrain setup conda
to query the latest version and explicitly install that, just like nextstrain update conda
does (c.f.).I think (2) makes the most sense. In the meantime, testing that any version is installable is still useful, and when we update Nextstrain CLI for (2) this workflow will start always testing the latest version.
Updated. Test run worked. Merging.
…to catch issues like the one in monkeypox CI¹ earlier. Since successful installation relies on external resources out of our control, we want to regularly test it to ensure we know when an external change breaks it.
* As it stands currently, this isn't strictly the latest package, just that there's some package version that's installable. To ensure the former, we'd have to query the latest version (e.g. similar to what devel/download-latest does) and pass it into setup-nextstrain-cli as an input, which would then pass it to
nextstrain
in NEXTSTRAIN_CONDA_BASE_PACKAGE.Alternatively, we're likely to update
nextstrain setup conda
anyway to query and install the latest version itself explicitly, just likenextstrain update conda
does, and so this workflow can simply wait for that change to happen.Resolves https://github.com/nextstrain/conda-base/issues/41.
¹ e.g. https://github.com/nextstrain/monkeypox/issues/177
Checklist