Bump staging to caa9bb

[github-actions]

@maverbiest wants to update the staging deployment from pathoplexus/pathoplexus@dfe7eb5 to pathoplexus/pathoplexus@caa9bb1.

Commit date: 2026-08-26T12:20:16Z

Changelog

• Adding zika virus pathoplexus#1069
• Add GA minutes summary from 3 Aug pathoplexus#1118
• Update URL in DEPLOYMENT_PROCEDURE.md pathoplexus#1117
• Minor updates to Citation page for clarification pathoplexus#1116
• Own and shrink organism images (ebola, WNV, CCHF, Andes) pathoplexus#1113
• Fix model annotation in claude code review action pathoplexus#1115
• feat(actions): Claude pr reviews pathoplexus#1114
• Pull YFV dataset from Nextclade Data now that it's released pathoplexus#1111
• Narrow Yellow fever clade column to 76px pathoplexus#1110

Comparison

pathoplexus/pathoplexus@dfe7eb5...caa9bb1

Pre-merge checklists

Before merging this PR and bumping the staging version, clone the production database to staging and confirm this was successful:

• DB clone: ssh bastion "cd pathoplexus/scripts/db-clone/ && ./clone-prod-to-staging.sh"
• Restart staging backend: kubectl rollout restart deployment/loculus-backend -n staging
• Run regressions tests to confirm staging is now identical to production (you will need to wait for SILO pods to import any new data)
  Only thing that showed up was changes to URL in version comments for 228 recently revoked mpox sequences. This is the producs of sed replacements in the db clone scripts rather than an actuall diff between prod and staging:

https://github.com/pathoplexus/pathoplexus/blob/04ba354ae38642b113c4bd35bc590012ede4dbda/scripts/db-clone/clone-prod-to-staging.sh#L37

228 rows changed

  accessionVersion: PP_001591C.2
    versionComment: "https://pathoplexus.org/about/governance/minutes/2026-06-01_EB_Resolutions.pdf" => "https://staging.pathoplexus.org/about/governance/minutes/2026-06-01_EB_Resolutions.pdf"

...

Post-merge checklists

After merging this PR, work through these checks (or provide justification for anything that was skipped) to confirm functionality and data integrity of Pathoplexus under the new version.

Standard checklist:

• Run regression tests, highlight any observed differences and discuss why they are expected. If the new version includes new preprocessing pipeline versions: wait for reprocessing to finish and for all new SILO pods to come up first
  Regression tests are clean (apart from URLs mentioned above). I did add Zika to the organism list (Adding zika to list of organisms in regression tests pathoplexus#1122), but of course there's no Zika on prod so no diff to compare.
• Confirm submit/revise/revoke flow works (also pay close attention to the UI, document anything out of the ordinary):
  • Submit test data to the staging preview
    • Confirm submission goes through (I submitted zika example data! PP_007JJQR.1, PP_007JJRP.1, PP_007JJSM.1, ..., also CCHF: PP_007JK05.1)
  • Revise a test sequence (revising: PP_007JK05.1)
    • Confirm revision goes through (PP_007JK05.2)
  • Revoke a test sequence (PP_007JJSM.1)
    • Confirm revocation goes through (PP_007JJSM.2)

Rollout-specific checklist:

• Check to make sure Zika looks as expected
  • Data gets ingested, preprocessed, loaded into SILO
  • News post looks good (check links)