Update FRONTEND_VERSION for v2026.2.1 - #2098
Open
matthew-white wants to merge 1 commit into
Open
Conversation
29 tasks
latin-panda
approved these changes
Jul 30, 2026
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 prepares the patch release v2026.2.1. It updates
FRONTEND_VERSION.What has been done to verify that this works as intended?
The patch release hasn't actually been tagged yet in the
central-frontendrepo, so it is expected that CI currently fails on this branch. We can rerun CI once the release has been tagged incentral-frontend. Alternatively, we could check CI on thenextbranch once this PR is merged tonext. Either way, let's merge this PR tonextonly once the release has been tagged.Why is this the best possible solution? Were any other approaches considered?
Even though the release hasn't been tagged yet in
central-frontend, I think it's OK to go ahead and review this PR. It's just one version number changing to another. You can compare this PR with the following previous PR: #2039