Bump staging to 4b9e4e

[github-actions]

@maverbiest wants to update the staging deployment from pathoplexus/pathoplexus@730ca18 to pathoplexus/pathoplexus@4b9e4e5.

Commit date: 2026-06-29T10:03:11Z

Changelog

• Update Loculus version to 6c6d2f pathoplexus#1059
• Style polished FAQ accordion for /about/faq page pathoplexus#1053
• Fix OutBreakHintBox due to Tailwind upgrade pathoplexus#1056
• Update docs for host metadata field to address waste water pathoplexus#1047
• Add EB resolutions 2026-06-02 pathoplexus#1004
• Hint about using all data in outbreak settings pathoplexus#1027
• Update Loculus version to 9cc8e1 pathoplexus#1054
• Update Loculus version to 89635e pathoplexus#1052
• Update Loculus version to fba408 pathoplexus#1051
• docs: drop obsolete post-revoke approval step from revoke guide pathoplexus#1049

Comparison

pathoplexus/pathoplexus@730ca18...4b9e4e5

[maverbiest]

To test after merging:

• ensure new backend comes up & migrations go through
  • Had to kill old backend for migrations to run (thanks for the tip, @anna-parker !)
• quick check of frontend changes (version diff etc.)

• do a test submission of cchf and ebola on staging, check it works well

  • submitted CCHF: https://staging.pathoplexus.org/seq/PP_00762L6.1

  • submitted ebola zaire: https://staging.pathoplexus.org/ebola-zaire/search?groupId=892&visibility_groupName=true&groupName=Epidemiology+and+Virus+Evolution%2C+Swiss+TPH%2C+Switzerland

  • can revise, new version shows up:

• can revoke, revocation shows up

• Let staging sit with the new changes for around an hour
• rerun regression tests
  • Only diffs due to the test submissions I made to staging
• rollout to prod
  • PR here: Promote staging to production: 4b9e4e536cde68d632cf8f8e73a067f40aadb8d2 #780

[anna-parker]

there are some db migrations (using flyway) in this rollout, you might need to temporarily kill the old backend if the new one has issues getting a lock