wow, this was even faster then the new version can be on bioconda :D

so what versions do we need to track now? pangolin version and pangolindata?

additionally which columns do we need to track? @RaverJay

@RaverJay iam currently tracking the following columns for the autobuild to ensure that they are present for your report, this would be fine?

"taxon," || exit 1; }
 ",lineage," || exit 1; }
",conflict," || exit 1; }
",pangolin_version," || exit 1; }
 ",scorpio_version," || exit 1; }
 ",constellation_version," || exit 1; }
 ",qc_status," || exit 1; }
 ",qc_notes," || exit 1; }

if yes ill start the build and post the new docker name here. ill need to add a few other commits on top of it too (so that e.g. --update works fine)

nanozoo/pangolin-v4:4.0--1.2.133

Pulling and testing now

The (new) report uses these columns:

taxon,lineage,conflict,scorpio_call,scorpio_conflict
version,pangolin_version,scorpio_version,constellation_version

Works now

awesome

"variants tableof" is missing a whitespace : )

"variants tableof" is missing a whitespace : )

fixed :D

Added nextclade private mutation information to the datatable ( closes #226 )
Somewhat unrelated, but a minor change

@RaverJay added the columns to the docker autobuild to check if they are present

• merging into release branch