Repository navigation
Require Beacon Web 2.1 - #261
Merged
Merged
Conversation
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.
Raises
MinWebVersionfrom 2.0.4 to 2.1.0 (served at/api/v1/info).Why: server 2.1's region, scope and advert pages answer 503 with Retry-After while a read model is not ready (first fill after an upgrade, repairs). Beacon Web 2.0.x does not wait those out and shows an empty or failed page; it also pages by the legacy millisecond cursor and skips rows tied on a page boundary. Web 2.1 handles both. With the floor at 2.1.0, a browser tab still running an older web build shows the reload screen instead.
Release note: deploy Beacon Web 2.1 together with server 2.1.
MinAppVersionstays 2.0.0 (no older app is released, and nothing in the API breaks 2.0 apps). Docs: beacon-docs upgrading.md (linked PR).