fix(deployments): align version/status/compute badges in worker deployments table#3489
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
bilal-karim
force-pushed
the
fix/deployment-badge-alignment
branch
from
4b3d98c to
72abb90
Compare
…yments table The "Latest Version (Build ID)" cell laid out the version link, status badge, and compute badge in a flex row with no width constraints, so varying version and status text widths pushed the badges to different x-positions on every row, making the column look ragged. The compute provider badge was also taller than the status badge. Give the version link a min-width (min-w-32) and the status badge a min-width with centered content (min-w-24 justify-center) so the three items snap to consistent columns across rows. min-w (rather than a fixed width) lets an unusually long build ID grow its own cell gracefully instead of overflowing into the badge. Drop the compute badge's larger padding and text-sm so it matches the status badge height. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bilal-karim
force-pushed
the
fix/deployment-badge-alignment
branch
from
72abb90 to
9560b0f
Compare
rossnelson
approved these changes
Jun 5, 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.
Problem
On the worker deployments page, the Latest Version (Build ID) cell lays out the version link, status badge, and compute badge in a
flexrow with no width constraints. Because the version text (v0.0.1-runbookvs1.0.0) and the status text (CurrentvsDrainedvsCreated) have different widths, every badge starts at a different x-position from row to row, so the column reads as ragged. The compute provider badge was also taller than the status badge, adding vertical inconsistency.Fix
Give the two left-hand items consistent widths so the items after them always start at the same x, and align the badge heights:
Copyable'scontainer-class(min-w-32 shrink-0).min-w-24 justify-center).text-sm(px-2 py-0.5 text-sm→px-1) so it matches the status badge height.Now each row resolves to the same three positions — version → status → compute badge — so they line up as columns of equal height. Using
min-wrather than a fixed width keeps the common case aligned while letting an unusually long build ID grow its own cell gracefully instead of overflowing into the status badge.Before / After
Testing
pnpm lint— clean (pre-commit lint-staged also ran eslint/prettier/stylelint).pnpm check— no new errors in the changed files.🤖 Generated with Claude Code