iiinova — where your digital self keeps evolving

robzepdev

@robzepdev.bsky.social

Frontend Dev (3 YOE) x AI Builder. robertoz.com 🛠️ Building Verdict: turns complex changelogs into grounded summaries, breaking changes, and migration steps. Understand before you upgrade. release-tracker-drab.vercel.app/tec…

Posts Replies Media

robzepdev @robzepdev.bsky.social · 15/10/2026

Three differences from the mocks came out of measuring, not looking: a row set at 14px where the mock says 13, a separator sitting under a row instead of over it, and a hand-drawn chevron missing its curve. None of the three is visible by eye.

The React 19.3.0 release page on Verdict: the verdict 'ok: safe to upgrade' in green, a panel with 0 breaking changes and 5 key points, and five key points each ending in a link to the release-notes line it was read from.

100 1

robzepdev @robzepdev.bsky.social · 15/10/2026

Then the ones the eye cannot catch. A clamp in vw inside a fixed column measures the wrong thing: above ~1340px 'ok: nothing needs action' asked for 346px inside a 326px panel. The copy never grew. The clamp grew with the viewport while the column stayed 360px.

The React page on Verdict in two columns. Left: the upgrade path from 19.0.0, and a panel titled 'note: 1 without a verdict' listing 30 releases, 1 safe to upgrade, 1 with no summary yet, 28 digest fixes you can skip. Right: the releases in upgrade order, with digests folded and 19.3.0 marked 'ok: safe to upgrade'.

100 1

robzepdev @robzepdev.bsky.social · 15/10/2026

I spent this week redoing the look of every screen in Verdict. The design work is the boring part of this thread. The interesting part is four things the browser was doing that I could not see, and one of them had been live and broken in production the whole time. 🧵

Verdict landing page, dark. Left: the headline 'Understand before you upgrade' and a line saying React 19.0.0 shipped 13 breaking changes across 271 lines of release notes. Right: a panel with four real lines of those notes, line 47 highlighted, under the verdict 'warning: action required'.

110 1

robzepdev @robzepdev.bsky.social · 01/10/2026

The AI summaries are live on the tracker now. Not a local build, not a mock: this is production, grounded on the official release notes only, with a line pointer next to every claim. 126 of them went out in a single batch. Here is what that actually cost me.

The React 19.3.0 page on the tracker, in production. A large verdict reads 'warning: action required', with 1 breaking change and 5 key points. Under the summary title a line says it comes from the release notes only, generated by claude-opus-5 with prompt v4. Each of the five key points ends with a link to a numbered line in the release notes.

100 1

robzepdev @robzepdev.bsky.social · 28/09/2026

The release tracker has accounts now. You follow the tools in your stack, and one page tells you what shipped in the last 30 days and whether upgrading needs work. Here is what I learned building it. 🧵

The dashboard of the release tracker, dark theme: the verdict reads ok, nothing needs action, then a counts line for the last 30 days across 3 technologies, a Spotlight with Vite 8.3.0, React 19.3.0 and a compact TypeScript row, a Previews section with two Vite betas, and a weekly digest folded by ISO week with week 39 open on Vite 8.3.1. Every row says no summary, because the summary jobs are off until launch. Screenshot from a production build running locally.

110 1

robzepdev @robzepdev.bsky.social · 26/09/2026

The tracker now runs on its own. At 02:00 UTC a cron asks npm and GitHub what is new; today it found Vite 8.3.1 and the public page updated itself. Nobody pressed anything. 🧵

The Vite page on the tracker, dark theme. The header reads: latest 8.3.1, npm vite, github vitejs/vite. Below it the v8 releases: 8.0.0 featured, 8.1.0, 8.2.0 and 8.3.0 notable, and the patches folded into digest rows.

110 1

robzepdev @robzepdev.bsky.social · 24/09/2026

Rule two: I never ask the model for line numbers. It counts badly, and it's wrong invisibly. It returns a verbatim quote. I search my stored copy of the notes for that quote and compute the lines myself. A quote I can't find exactly was invented, so it gets no pointer.

The raw release notes of React 19.2.0 shown with line numbers on a dark background. Line 20, about updated `prerender` APIs returning a `postponed` state, is framed and highlighted, having been reached by clicking a citation link in the summary above.

100 1

robzepdev @robzepdev.bsky.social · 24/09/2026

I'm building a tracker that reads every new release of React, TypeScript, Vite & co. and tells you whether you need to touch your code. The hard part isn't writing the summary. It's proving the model didn't make it up. 🧵

A release page for React 19.2.0 on a dark background. A large heading reads 'warning: action required', with '2 breaking changes' and '5 key points' underneath. Five key points are listed, each ending in a link like 'release-notes:7' that points back to a line of the official notes. Local preview; summaries are not switched on in production yet.

110 1