Starred repos weekly — Jun 22-28, 2026

VS Code 1.126 is the only stable release inside the Jun 22-28 window, so it gets the only clear "upgrade now" call this week. Next.js shipped more 16.3 preview/canary builds, while React, Rust, and Tailwind stayed on their earlier stable lines.

One-line progress

Next.js: v16.2.9 remains the latest stable, but the 16.3 preview/canary train kept moving through Jun 25-28; treat it as test-lane signal, not a production upgrade. 1 2 3
VS Code: 1.126 landed on Jun 24 with session-level chat cost, multiple chats in one agent-host Copilot session, and safer first-open workspace trust defaults; upgrade if you use Copilot agents or often inspect unfamiliar folders. 4 5
React: v19.2.7 is still the latest stable release from Jun 1, while this week's commits were mostly DevTools and release-process maintenance. 6 7
Rust: 1.96.0 remains current; this week showed normal compiler rollup activity rather than a new stable release. 8 9
Tailwind CSS: v4.3.1 is still current, and late-week commits point to release housekeeping plus pnpm v11 migration work; hold unless a v4.3.1 fix maps to a bug you hit. 10 11 12

Repo notes

Next.js: preview activity, stable users hold

The latest stable release is still v16.2.9, published Jun 10 as an empty release to make next@latest point at a stable version after Trusted Publishing constrained dist-tag edits. 1 Inside this week's window, Next.js published v16.3.0-preview.5 on Jun 25 and continued canary work through v16.3.0-canary.70 on Jun 28. 2 3

The hot-watch item is still operational rather than feature-level: issue #54708, "Next.js development high memory usage," is open with 164 comments, and #49279 on App Router plus Framer Motion shared layout animations is open with 142 comments. 13 14

Upgrade call: Hold for production stable users. Try the 16.3 preview/canary line only if you are already testing Turbopack or canary-specific fixes.

VS Code: upgrade for agent-heavy workflows

VS Code 1.126 was published Jun 24. The official notes list three changes that matter for day-to-day users: session-level cost information for chat, multiple chats inside one agent-host Copilot session, and opening new folders in Restricted Mode by default instead of interrupting immediately with a trust prompt. 4 5

The long-tail issue queue has not changed much at the top. The most-commented open issues remain workbench font customization (#519, 594 comments) and mouse shortcut customization (#3130, 453 comments). 15 16

Upgrade call: Yes. The cost view alone is useful if Copilot chat spend matters, and Restricted Mode is a safer default for quick repo inspection.

React: no stable bump this week

React's latest stable line is still v19.2.7, released Jun 1 to fix missing FormData entries in Server Actions after a 19.2.6 regression. 6 This week's visible commits were maintenance-oriented, including a DevTools change that adds disclosure for ignore-listed stack frames. 7

For open threads, the biggest discussion remains #13991 on hooks with multiple React instances at 515 comments. The older custom element attributes/properties RFC, #11347, is still open with 286 comments. 17 18

Upgrade call: Conditional. Move to 19.2.7 if you use Server Actions and want the FormData fix; otherwise there is no new weekly release pressure.

Rust: stable stays at 1.96.0

Rust 1.96.0 remains the current stable release. Its release notes include language fixes, LoongArch and Fuchsia target updates, new stabilized range APIs, Cargo registry/git dependency handling, and fixes for CVE-2026-5222 and CVE-2026-5223. 8 During Jun 22-28, the public commit stream showed normal rollups and compiler-internal work rather than a release event. 9

The most-commented open PR is still the "do not merge" CI experiments PR #112049 with 2,006 comments. The next large open PR in the issue tracker sample is #113382, a perf test PR with 495 comments. 19 20

Upgrade call: Hold if you already moved to 1.96.0. Upgrade from older 1.95.x or below if you need the Cargo fixes or stabilized range APIs.

Tailwind CSS: v4.3.1 remains the practical target

Tailwind CSS v4.3.1, published Jun 12, is still the latest release. It added a --silent option for the CLI and fixed a long list of v4.3 issues, including Node 26 deprecation warnings, @apply with CSS mixins, source glob handling, and Vite sourcemap warnings. 10 This week's commits included release-process cleanup and a pnpm v11 migration, but no new public release. 11 12

Two watch items are worth keeping on your upgrade checklist: #15005 reports that @property is not supported in shadow roots, and #17958 tracks the musl/Alpine-style lightningcss.linux-x64-musl.node module error. 21 22

Upgrade call: Conditional yes. Move to v4.3.1 if its fixes match your build pipeline; hold on Alpine or musl-heavy deployments until you verify #17958 against your environment.

Quick reference

Repo	Latest release checked	This week's signal	Hot open item	Upgrade call
Next.js	v16.2.9, Jun 10 1	16.3 preview/canary builds through Jun 28 2 3	Dev memory usage, #54708, 164 comments 13	Hold
VS Code	1.126.0, Jun 24 4	Chat cost visibility, multi-chat agent sessions, safer folder trust defaults 5	Workbench font customization, #519, 594 comments 15	Yes
React	v19.2.7, Jun 1 6	DevTools and release-process maintenance commits 7	Multiple React instances with hooks, #13991, 515 comments 17	Conditional
Rust	1.96.0, May 28 8	Normal rollups, no stable release in window 9	CI experiments PR, #112049, 2,006 comments 19	Hold if already on 1.96.0
Tailwind CSS	v4.3.1, Jun 12 10	Release cleanup and pnpm v11 migration commits 11 12	Shadow-root `@property`, #15005, 33 comments 21	Conditional