Starred repos weekly — Aug 10–16, 2026: VS Code 1.133 and Next.js 16.3.1 are the upgrades

VS Code 1.133.0 is the week's clearest upgrade. Next.js also crossed an important line: stable v16.3.1 shipped on Aug 13, while the repository's newest tag is still the canary v16.3.1-canary.21 from Aug 16. React, Rust, and Tailwind CSS had no release between Aug 10 and Aug 16; their latest public tags remain v19.2.8, 1.97.1, and v4.3.3, respectively. 1 2 3 4 5 6 7

One-line progress

Next.js: v16.3.1-canary.21 shipped Aug 16 with async-local-storage anchoring, a deflake for use-cache warm reloads, and more Turbopack/router work; stable v16.3.1 arrived Aug 13 with a larger backport set covering Turbopack, image responses, cache invalidation, HMR, and routing. 3 4
VS Code: 1.133.0 shipped Aug 12 with model-provider switching in Claude sessions, an experimental signed-out Agents window, sticky chat prompts, and automatic HTML preview reloads. 1 8
React: No release landed in the window; v19.2.8, released Jul 21, remains the latest tag and improves React Server Components decoding performance. 5 9
Rust: No release landed in the window; 1.97.1, released Jul 16, remains the latest tag and fixes an LLVM-optimization miscompilation in rustc. 6 10
Tailwind CSS: No release landed in the window; v4.3.3, released Jul 16, remains the latest tag and fixes polling watch mode, preprocessor rebuilds, CSS nesting without Lightning CSS, and Windows CJK font selection. 7 11

github.com · Repositorio de GitHub

microsoft/vscode

https://github.com/microsoft/vscode

Cargando tarjeta de contenido…

Upgrade calls

Next.js — Yes for stable 16.3.1; hold the canary

If you are on the 16.3 line, v16.3.1 is the release to validate and adopt. Its backports fix several Turbopack paths, preserve optimized image responses, keep the dev validation worker alive across HMR, tighten cache invalidation, and fix repeated prefetch loops. The newer canary train is useful for a test lane, but v16.3.1-canary.21 contains ongoing experimental work rather than a reason to move production to canary. 3 4

The two most-commented currently open issues returned for Next.js are both concrete reasons to test your own stack:

#49279 — 142 comments: App Router shared-layout animations can fail with Framer Motion. The report describes a navigation highlight that does not slide when the route container re-renders. 12
#64921 — 104 comments: App Router can resolve CSS in a different order between development and production. The report covers next dev, next build, next start, and deployed Vercel runs. 13

VS Code — Yes

Install 1.133.0 if you use agent workflows or the integrated browser. Claude sessions can switch between Anthropic and Copilot model providers between turns; the experimental chat.agentHost.allowSignedOutWhenUsable setting lets Claude users open the Agents window without GitHub sign-in; and workbench.browser.autoReloadOnFileChange refreshes local HTML previews as files change. VS Code rolls the release out gradually, so use Check for Updates if it has not appeared yet. 8

The provider switch has a direct cost boundary: Anthropic models use the configured API key, while Copilot models use the Copilot subscription. The signed-out Agents window currently supports Claude; Copilot with personal model keys and Codex are planned rather than included in this release. 8

The most-commented currently open workbench threads remain long-standing feature gaps rather than 1.133 regressions:

#519 — 600 comments: users want independent font and font-size controls for the workbench instead of changing editor settings or using zoom. 14
#3130 — 453 comments: users want to customize mouse-plus-modifier shortcuts, such as Alt-click to add a selection, alongside keyboard shortcuts. 15

React — Hold

React has no release-driven action for this window. v19.2.8 from Jul 21 remains the latest public tag, with a targeted React Server Components decoding performance improvement. If you already run that patch, hold; if you are behind it, treat the move as catch-up rather than a response to a new weekly release. 5 9

The two most-commented currently open React discussions are useful diagnostics for different kinds of applications:

#13991 — 515 comments: multiple React instances can trigger the misleading Hooks error even when the component uses Hooks correctly. Check dependency resolution before debugging the component itself. 16
#11347 — 286 comments: an RFC discussion weighs how React should pass attributes and JavaScript properties to custom elements, including server-rendering and compatibility trade-offs. 17

Rust — Yes, after CI

Rust has no new release in the window, but 1.97.1 is still the patch to validate if your toolchain has not moved. It backports an LLVM fix for a rustc optimization miscompilation and reverts one known trigger on the compiler side. Run compiler, benchmark, and release CI before putting it on every build machine. 6 10

The formal comment leader is open PR #112049 — 2,241 comments, a do not merge thread for CI experiments. It is a signal about compiler-project infrastructure, not an application dependency to adopt. The practical watch is issue #32838 — 495 comments, the long-running allocator-traits and std::heap tracking issue; its page now directs active discussion to the dedicated allocator working group because the original summary is outdated. 18 19

Tailwind CSS — Conditional

There is no Tailwind release in the window. v4.3.3 remains the sensible patch if you use @tailwindcss/cli --watch where filesystem events are unreliable, depend on Sass or another preprocessor, or need CSS nesting to work when Lightning CSS is not running. Windows projects with CJK text also get more predictable page-language font selection. 7 11

Keep the call conditional for two environment-specific edges:

#17958 — 38 comments: an Alpine or other musl-based container can fail to load lightningcss.linux-x64-musl.node during a Next.js build. The issue is labeled upstream and remains open. 20
#15005 — 33 comments: Tailwind v4's @property definitions do not work inside shadow roots. Web Components may need the definitions attached to the base document or another project-specific workaround. 21

Quick reference

Repo	Latest checked release	In-window?	Most-commented open item	Upgrade call
Next.js	`v16.3.1-canary.21`, Aug 16 4; stable `v16.3.1`, Aug 13 3	Yes: canary + stable	#49279, App Router + Framer Motion, 142 comments 12	Yes for stable; hold canary
VS Code	`1.133.0`, Aug 12 1	Yes	#519, workbench font controls, 600 comments 14	Yes
React	`v19.2.8`, Jul 21 9	No	#13991, multiple React instances, 515 comments 16	Hold
Rust	`1.97.1`, Jul 16 10	No	#112049, CI experiments, 2,241 comments; practical watch #32838, 495 18 19	Yes, after CI
Tailwind CSS	`v4.3.3`, Jul 16 11	No	#17958, musl Lightning CSS module, 38 comments 20	Conditional

Comment counts are the current totals on the open issues or PRs when checked on Aug 17, 2026; they are not comments added during Aug 10–16.

Fuentes de referencia

1
VS Code 1.133.0 release
github.com
2
VS Code releases
github.com
3
Next.js v16.3.1
github.com
4
Next.js v16.3.1-canary.21
github.com
5
React releases
github.com
6
Rust releases
github.com
7
Tailwind CSS releases
github.com
8
Visual Studio Code 1.133 update notes
code.visualstudio.com
9
React v19.2.8
github.com
10
Rust 1.97.1
github.com
11
Tailwind CSS v4.3.3
github.com
12
Next.js issue #49279
github.com
13
Next.js issue #64921
github.com
14
VS Code issue #519
github.com
15
VS Code issue #3130
github.com
16
React issue #13991
github.com
17
React issue #11347
github.com
18
Rust PR #112049
github.com
19
Rust issue #32838
github.com
20
Tailwind CSS issue #17958
github.com
21
Tailwind CSS issue #15005
github.com