[DO NOT MERGE]: upgrade @vercel/geistdocs to 1.17.1 - #3170
[DO NOT MERGE]: upgrade @vercel/geistdocs to 1.17.1#3170christopherkindl wants to merge 9 commits into
Conversation
Picks up the new footer (Footer no longer takes a config prop), the heading font-weight change to 450, and the tightened navbar OSS-menu marks. Also switches the site's own navbar logo from the vendored geistcn LogoWorkflow fallback to the package's LogoWorkflowSdk, using its new tuned default height instead of a hardcoded 15. Fixes a resulting regression: navbarOssProducts entries lacked an `id`, so resolveOssProducts' `product.id !== activeProduct` filter evaluated to `undefined !== undefined` (false) for every entry and emptied the OSS flyout. Added stable `id`/`label` values to each entry.
…ride The manual navbarOssProducts array (with local logo imports/heights) is no longer needed now that the package's DEFAULT_OSS_PRODUCTS list already includes all these SDKs with proper id/label/section values. navbarActiveProduct: 'workflow-sdk' now handles self-exclusion instead.
The docs, cookbook, and v5 route layouts plus the shared DocsLayout container hardcoded bg-background-100 (pure white), so /docs/* pages rendered on a lighter surface than the rest of the site. Switch them to bg-background-200, matching the geistdocs template's page background.
The marketing homepage headings hardcoded font-semibold (weight 600) plus manual responsive sizes/tracking, so they rendered heavier than the docs headings that now use Geist's 450 heading weight. Swap each display heading to the package's text-heading-* utilities, which bundle the 450 weight, line-height, and tracking, mapped across breakpoints to the nearest design-system size. Inline label/emphasis spans keep their own weight.
Extends the homepage heading change to the /worlds section: the world listing, detail, compare, and building-a-world pages plus their components hardcoded font-semibold display headings. Swap each to the package's text-heading-* utilities (450 weight + line-height + tracking), mapped across breakpoints to the nearest design-system size. Mono stat numbers, per-benchmark item labels, and the dialog title keep their own weight.
The homepage sections were wrapped in a grid divide-y border-y sm:border-x container, drawing side borders and divider lines between every section. Drop that framing so the sections flow with whitespace separation.
Drop the divide-x column dividers still drawn inside the use-cases (3-col), feature-grid (2-col), and templates sections, so no vertical lines remain after the section-grid removal. Section padding keeps the columns visually separated.
The two 2-col feature blurbs ("Deep integration with AI SDK.",
"Durable agents by default.") hardcoded their size/leading/tracking
plus font-medium/font-semibold weights. Those manual sizes already
equal text-heading-20/24, so swap to text-heading-20 lg:text-heading-24
— same sizes, but the Geist 450 heading weight (lead drops 600 -> 500
via the utility's [&>strong] rule). The lead stays gray-1000 for
emphasis; body stays gray-900.
|
🧪 E2E Test Results✅ All tests passed E2E Test SummarySummary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
✅ vercel-multi-region
|
📊 Workflow Benchmarkscommit Backend:
ℹ️ Metric definitions & methodologyBest/P75/P90/P99 deltas compare against the most recent benchmark run on Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window) Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost 🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120 All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor ( Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the |
Summary
Upgrades the docs app to
@vercel/geistdocs@1.17.1and applies the follow-on styling to match the new Geist heading system.@vercel/geistdocs1.14.0 → 1.17.1; adopt the package'sLogoWorkflowSdk(new artwork at its tuned default height) and fix the<Footer />prop removal.navbarActiveProduct: 'workflow-sdk'instead of a hand-maintainednavbarOssProductsoverride.bg-background-200to match the template.text-heading-*utilities (Geist 450 weight) across the homepage and/worldsheadings, plus the feature-grid paragraph text.rounded-full.Verification
pnpm --filter docs buildpasses.