Repository navigation
Show region coverage on the deployments list - #3998
Draft
rossnelson wants to merge 1 commit into
Draft
rossnelson wants to merge 1 commit into
rossnelson wants to merge 1 commit into
Conversation
Third slice, on top of the per-region Version detail. Still dark unless a consumer passes the Namespace's regions: fewer than two and every row renders exactly as it does today. Each version in the list now carries a badge per region, beside the provider badge it already has. Only a region nothing serves is coloured. Colouring every region would make the ordinary case look alarming and leave the one that matters — a region a failover would find empty — to blend in with the rest. The list already has what this needs: a version summary carries its whole compute config, so the regions come from data the row has rather than another request. The page takes the regions and passes them down, which is the same shape the Version detail uses, so a consumer wires both the same way.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rossnelson
marked this pull request as draft
October 8, 2026 16:19
This branch was successfully deployed
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
1 participant
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.
Third slice of multi-region Serverless Workers. Still dark unless a consumer passes the Namespace's regions — fewer than two and every row renders exactly as it does today.
Description & motivation 💭
Each version in the deployments list now carries a badge per region, beside the provider badge it already has.
Only a region nothing serves is coloured. Colouring every region would make the ordinary case look alarming and leave the one that matters — a region a failover would find empty — to blend in with the rest. In a list the job is to draw the eye to the exception, not to label the norm.
No extra requests
The list already has what this needs. A version summary carries its whole compute config, so coverage is derived from data the row holds. Nothing new is fetched.
Design Considerations 🎨
namespaceRegionsand passes it down, so a consumer wires both surfaces the same way.data-region-matchand the tests assert that rather than the rendered text.Testing 🧪
How was this tested 👻
5 new component tests: the gate in both forms, a badge per region with the cloud prefix stripped, only the uncovered region coloured, and a fully covered row left plain.
301 tests pass across deployments, services, utilities and pages.
count-strict-errors.tsreports 0.The one lint warning in
deployments.svelte(require-each-key) is pre-existing — confirmed by stashing this branch and re-running.What comes next
Checklists
Merge Checklist