Promote staging to production: 1c0403207822001d3cc850b67424636f2ef8ac05 - #802
Merged
maverbiest merged 1 commit intoAug 3, 2026
Conversation
anna-parker
approved these changes
Aug 3, 2026
maverbiest
deleted the
promote-to-production-1c0403207822001d3cc850b67424636f2ef8ac05
branch
August 3, 2026 12:17
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
2 participants
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.
maverbiest wants to promote the current staging SHA to production.
Staging SHA: 1c0403207822001d3cc850b67424636f2ef8ac05
Please review and approve to deploy this version to production.
Notes
This is just to clean up old pipeline version from the previous rollout: pathoplexus/pathoplexus#1089.
I ran the regression tests while this was on staging, which reported no differences between staging and production.
I do still see the previous pipeline versions listed in the admin dashboard after they've been removed from the config, but as far as I know this is expected behaviour as the backend keeps the current pipeline version - 1 in the DB as well (please shout if not!). https://github.com/loculus-project/loculus/blob/82a452b8730e4696d9507a2b8e08eb9bd0bd03b8/backend/src/main/kotlin/org/loculus/backend/service/submission/UseNewerProcessingPipelineVersionTask.kt#L32-L36