Bump staging to a12f63

[github-actions]

@maverbiest wants to update the staging deployment from pathoplexus/pathoplexus@356c03b to pathoplexus/pathoplexus@a12f630.

Commit date: 2026-08-28T08:27:11Z

Changelog

• Update Loculus version to 7db348 pathoplexus#1132
• Set the ingest batch size to 1000 pathoplexus#1129
• Clean up old dengue pipeline version pathoplexus#1131
• feat(db-clone): do not perform sed replacements on protected url in version comments, add env file with rds pghost info pathoplexus#1128

Comparison

pathoplexus/pathoplexus@356c03b...a12f630

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)

DB clone & backend restart were performed in the course of testing pathoplexus/pathoplexus#1128. I did run the regression tests to ensure staging and prod were equal, which showed 0 differences for all organisms.

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 showed zero differences for all organisms

• 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 (Zika: PP_007JSHX.1, PP_007JSJV.1, PP_007JSKT.1; CCHF: PP_007JSG0.1)
  • Revise a test sequence (PP_007JSKT.2)
    • Confirm revision goes through
  • Revoke a test sequence (PP_007JSG0.1)
    • Confirm revocation goes through

Rollout-specific checklist:

• Test submission of xz compressed metadata file through website gets rejected