Schema validation for pathogen.json does not reject unknown fields or catch typos

New flu_h3n2_ha datasets not available from nextclade-cli dataset get command

Warning in release script: WARNING: "nextstrain/mumps/sh: Reference sequence provided does not exactly match reference (root) sequence in Auspice JSON. This warning signals that there is a potential for failures if the mismatch is not intended."

Influence H3N2 and H1N9pdm HA datasets duplicate names

Deployments broken due to gh token permissions issue

Quality Control (QC)

Is RSVB G clade missing from latest release

Unexpected behavior: Nextclade ignores CDS unlinked to gene if gene is in gff3

Questions about creating a custom RSVA nextclade dataset with NC_038235 reference

While doing a release, it seems the dataset that's getting released is broken (getting 404)