Bump staging to 638f2c

[github-actions]

@maverbiest wants to update the staging deployment from pathoplexus/pathoplexus@a12f630 to pathoplexus/pathoplexus@638f2c3.

Commit date: 2026-09-08T08:23:12Z

Changelog

• Update Loculus version to 94efc2 pathoplexus#1136

Comparison

pathoplexus/pathoplexus@a12f630...638f2c3

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)

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
• 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 (CCHF: PP_007L258.1)
  • Revise a test sequence (paste AccessionVersion here)
    • Confirm revision goes through
  • Revoke a test sequence (paste AccessionVersion here)
    • Confirm revocation goes through

Rollout-specific checklist:

• Check Zika viral UShER linkout

[maverbiest]

Superceded by #839