Repository navigation
Update Backend/Frontend for v2026.3.1 - #2269
Merged
Merged
Conversation
43 of 44 tasks
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.
This PR updates Central Backend and Central Frontend for v2026.3.1:
serversubmodule for BackendFRONTEND_VERSIONThis PR intentionally targets the
masterbranch. These are the only things that will change with v2026.3.1. No op/infra has changed.What has been done to verify that this works as intended?
Tests should pass before we merge.
Why is this the best possible solution? Were any other approaches considered?
Following the release checklist #2267.