Starred repos weekly — Jul 6-12, 2026

VS Code and Rust both moved inside the Jul 6-Jul 12 window. VS Code 1.128 is the day-to-day workflow upgrade; Rust 1.97.0 is the toolchain upgrade to schedule after CI. Next.js kept its canary lane active, while React and Tailwind stayed on their June release lines.

One-line progress

Next.js: Latest in-window release is v16.3.0-canary.84, with the first three pieces of request-insights plumbing for dev snapshots, request history, fetch data, and local framework spans; latest stable remains the Jul 1 v16.2.10, which only filled a missed @next/swc-wasm-web publish. 1 2
VS Code: 1.128.0 landed on Jul 8 with multi-chat Claude agent sessions, workspace-less quick chats, Copilot Vision generally available, configurable integrated-browser tab placement, and OS-level keyboard shortcuts. 3
React: Latest public release is still v19.2.7 from Jun 1, so there is no fresh release action this week. 4
Rust: 1.97.0 shipped on Jul 9 with language lint changes, stabilized APIs, Cargo config improvements, and a long compatibility-notes section that deserves a CI pass before broad rollout. 5
Tailwind CSS: Latest release remains v4.3.2 from Jun 29; no new in-window patch changed the upgrade call. 6

Upgrade calls

Next.js - Hold for stable

The canary line is useful if you are testing the request-insights work early. The latest in-window canary, v16.3.0-canary.84, exposes dev snapshots to tools and HMR, derives request history and fetch data, and records local framework spans. 1

That is instrumentation work, not a broad production upgrade signal. The latest stable, v16.2.10, was outside this week's window and says it contains no code changes except publishing @next/swc-wasm-web, which had been missed since 16.2.4. 2 Keep production apps on stable unless you specifically need the canary request-insights path.

The hot open items are still framework-integration pain points: development high memory usage has 166 comments, and App Router plus Framer Motion shared layout animations has 142 comments. 7 8

VS Code - Upgrade

VS Code 1.128 is the clearest user-facing upgrade this week. Multi-chat Claude agent sessions let related chats live inside one Claude session, quick chats work without opening a workspace, and Copilot Vision can now take images and PDFs in Chat. 3

Two smaller items also matter if you live in editor-agent loops: integrated browser tabs can open in the active group, a side group, or a separate window; OS-level keyboard shortcuts can trigger VS Code commands even when VS Code is not focused. 3 The most-commented open issues are still long-running UX asks, not 1.128 regressions: workbench font control at 597 comments and mouse shortcut customization at 453 comments. 9 10

React - Hold

React has no in-window release to act on. v19.2.7 remains the latest public React line in the tracked repo, and that June patch fixed missing FormData entries in Server Actions after a 19.2.6 regression. 4

The most-commented open issues are still architectural watch items: hooks with multiple React instances at 515 comments, and the React 19 custom-elements attributes/properties RFC at 286 comments. 11 12 If you ship micro-frontends, embeddable widgets, or custom elements, keep those threads on your radar. Otherwise, hold.

Rust - Upgrade after CI

Rust 1.97.0 is worth scheduling, but read the compatibility notes before you hit merge. The release stabilizes Cargo's build.warnings config for treating local-package lint warnings in CI, stabilizes resolver.lockfile-path for custom lockfile locations, adds a shorter cargo -m alias for --manifest-path, and removes curl from the crates-io crate dependency path. 5

The compatibility notes are the reason not to treat this as a blind bump. Rust will use v0 symbol mangling by default, which can affect old debuggers and profilers; pin! no longer allows an unsound deref coercion; and several diagnostics or validations become stricter. 5 Run the toolchain upgrade through CI, then roll it forward if your profiler/debugger path and pinned-code assumptions are clean.

The noisiest open Rust item remains contributor infrastructure: the CI experiments PR has 2,110 comments. 13 For application teams, the allocator traits and std::heap issue is the more product-relevant long-running thread, at 490 comments. 14

Tailwind CSS - Conditional

Tailwind did not ship a new release inside the window. v4.3.2 is still the current release, and the June patch remains useful if you hit CLI watch crashes on Windows, Deno 2.8.x crashes in @tailwindcss/vite, HMR crashes when scanned files disappear, Template Toolkit or Maud class extraction, @source over-scanning, or newer PostCSS type errors. 6

Keep the same caveat as last week: the shadow-root @property issue is the top open Tailwind item at 33 comments, and the musl/Alpine lightningcss module issue is still open at 28 comments. 15 16 Upgrade if the fixed edge cases match your stack; hold if your build depends on Alpine or musl-based images until you verify the container.

Quick reference

Repo	Latest checked release	In-window?	Hot open item	Upgrade call
Next.js	`v16.3.0-canary.84` 1	Yes, canary	Dev high memory usage, 166 comments 7	Hold
VS Code	`1.128.0` 3	Yes	Workbench font size/font, 597 comments 9	Upgrade
React	`v19.2.7` 4	No	Hooks with multiple React instances, 515 comments 11	Hold
Rust	`1.97.0` 5	Yes	CI experiments PR, 2,110 comments 13	Upgrade after CI
Tailwind CSS	`v4.3.2` 6	No	Shadow-root `@property`, 33 comments 15	Conditional

Comment counts are total comments on currently open issues or PRs at collection time, not comments added during the Jul 6-Jul 12 window.