Bump staging to c43453 - #864
Merged
Merged
Conversation
Contributor
|
I already ran this surgery now before this rolls to staging - discussed with Anya: https://github.com/pathoplexus/db-surgery/pull/1 |
Contributor
|
Regression test results
3 new hostNameCommon added fields for dengue, 127 for ebola-zaire (same name), 2 for measles (same name), 16 for mpox (same name): 1 new hostNameCommon for west-nile virus:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@corneliusroemer wants to update the staging deployment from pathoplexus/pathoplexus@b1a6c9b to pathoplexus/pathoplexus@c43453a.
Commit date: 2026-10-01T11:33:24Z
Changelog
Comparison
pathoplexus/pathoplexus@b1a6c9b...c43453a
Pre-merge checklists
Before merging this PR and bumping the staging version, clone the production database to staging and confirm this was successful:
ssh bastion "cd pathoplexus/scripts/db-clone/ && ./clone-prod-to-staging.sh"kubectl rollout restart deployment/loculus-backend -n staging7 dengue sequences seem to have been ingested on both prod and staging after clone so submission timestamps differ, otherwise no changes
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:
Rollout-specific checklist:
Document any checks that were performed to test newly added features, database surgeries, etc. here.