Starred repos weekly — Oct 19–25, 2026: VS Code 1.143 makes the Copilot harness the default, Next.js ships 16.4.3
A five-repo scan for October 19–25: VS Code 1.143 makes the Copilot harness the default for new sessions and patches itself the same night, Next.js backports five runtime fixes in 16.4.3, and React, Rust, and Tailwind CSS publish nothing.
The completed week was October 19 – 25, 2026. Two of the five tracked repositories published a stable release: VS Code
1.143.0 on October 22, patched the same night 1, and Next.js 16.4.3 on October 23 2.React, Rust and Tailwind CSS published nothing.
Take the VS Code update first if you take either one. It changes which harness a new chat session runs on. The Next.js release is a backport of bug fixes with nothing new in it.
Comment counts below are the total comments on each open issue or pull request in this snapshot. A thread that opened years ago carries a large number whether or not anyone touched it this week.
Next.js
vercel/next.js published
16.4.3 on October 23 2. The notes describe a backport release, carrying fixes pulled across from the lts-active branch and none of the pending canary work 2.Five of the backports touch how an application runs. Extensionless Google font URLs now resolve in both bundlers,
proxy.ts stops loading the app-page runtime, and a Turbopack loader-invalidation change was reverted 2.The remaining two touch observability and startup: OpenTelemetry request traces stay together across middleware and adapters, and the server bootstrap stops loading a standalone copy of React 2.
What remains on the list is release machinery: release-bot credentials moved behind GitHub environments, un-drafting became a separate job, and a test dependency was pinned 2.
One new API arrived on canary during the week. PR #99871 gives
Link three named prefetch values — "shell", "prefetch" and "navigation" 5. Only "navigation" adds behaviour: it prefetches past an await navigation() boundary that a normal prefetch respects 5. The pull request merged on October 19, so the option lives in canary builds and in no stable release yet 5.The comment leaders barely moved. #49279 sits at 145 comments, two more than last week, and was last touched on October 24 after a quiet September 6. #64921 holds 109 and last moved on October 9 7.
Inside the window, #53473, on the
no-html-link-for-pages rule and pageExtensions, reached 79 comments on October 25 8. #91396, on the dev server's memory use, reached 31 on October 23 9.- Why included now:
16.4.3is the first stable on the 16.x line since16.4.2on October 15, and the only thing on that line to install this week. - Upgrade call — Yes: To
16.4.3if you are on16.4.0,16.4.1or16.4.2. It carries the October 14 patches and these backports.
Loading content card…
VS Code
microsoft/vscode published
1.143.0 on October 22 1. 1.143.1 followed the same night, and its whole content is one pull request bumping the bundled remote Node.js to 24.22.1 1011.The Copilot harness is now the default for new sessions. A new session starts on Copilot, built on the Copilot SDK and running through Agent Host, and you can keep it running in the editor window or pick it up in the Agents window 12.
The new default also changes two things a team may already have configured. Where your organization sets managed model defaults, new Copilot harness chats use them even when your own
chat.defaultModel names another model; the picker explains which default applied 12.Where policy requires the Copilot harness, the Local entry now stays visible in the picker as disabled, with a Learn why link, instead of disappearing 12. Administrators who need Local available keep
vscode.temporaryDefaultToLocalHarness 12.Compare Models (preview) runs one prompt against two or more models or harnesses, each in its own session, then offers a judge model to score the attempts and a Synthesize action to build on the recommended one 12.
On-device models are experimental and narrow. You download MAI Code 1.1 Flash from a new On This Device tab, point
chat.copilot.localModel.llamaServerPath at a llama-server build and enable the setting; the hardware floor is an NVIDIA GPU with 96 GB of memory or more, plus GitHub sign-in 12.One change reaches beyond the agent features. The editor now highlights up to 5,000 diagnostics per file, up from 500, while each extension's collection stays capped at 1,000 12.
Large Agent Host chats also open faster: a 1,150-request chat went from 35.6 s to 9.0 s on a cold open, and the window's longest freeze during that open fell from 28.3 s to 0.6 s 12.
The comment leaders did not move: #519 at 604 comments, last touched October 10, and #3130 at 453 1314.
Five threads moved inside the window. #13960, on virtual space, reached 317 comments on October 23, and #4490, macro recording, 280 on October 21 1516.
#43188, on opening several workspaces in one window, reached 220 on October 20, and #339363, on granular control over Copilot changes, 207 on October 25 1718. #5595, on scoping settings by platform, reached 187 on October 24 19.
- Why included now:
1.143.0is a new minor on the stable channel, with a same-night patch behind it, and the harness default changes where a new chat session runs. - Upgrade call — Conditional: Take it for model comparison, worktree cleanup or on-device models. Before updating, check whether managed model defaults will override the model you pinned, and whether new sessions should start on the Copilot harness.
Loading content card…
React
react/react, the canonical public repository behind the
facebook/react whitelist entry, published nothing this week. 19.3.1 from October 14 is still the newest release 20.Eight commits landed on
main, and five of them are correctness fixes around prerendering and hydration. PR #37916 makes useId values unique in large trees 21.PR #37901 fixes truncated Fizz prerender output under backpressure, and PR #37853 preserves the rendered shell when a synchronous prerender aborts 2223.
Two more land in the same area. PR #37876 lets
resumeAndPrerender postpone an existing boundary again, and PR #37856 strips the full <anonymous>. prefix from Flight I/O names 2425.Three commits come from compiler work. PR #37975 keeps declared Freeze effects on values that are already frozen during ref validation, and PR #37895 allows ref access inside
ResizeObserver and MutationObserver callbacks 2627.The comment leaders are unchanged: #13991 at 515 comments, last touched July 10, and #11347 at 286, last moved in 2024 2829.
The busiest thread that moved was #32950, a compiler bug about missing branch coverage, at 30 comments on October 20 30. #26608, on a
MessageChannel in the scheduler keeping Jest from exiting, reached 27 on October 21, and #34045, compiler false positives on synchronous setState in effects, 20 on October 23 3132.- Why included now: Eight commits landed with nothing published, and the fixes cluster in prerendering.
- Upgrade call — Hold:
19.3.1remains the version to be on, including the October 14 patches. Nothing from this week's commits is in a release yet.
Loading content card…
Rust
rust-lang/rust published no release.
1.99.1 from October 16 is still the newest stable 33, and 632 commits landed on main during the week.Three stabilization pull requests merged, all of them for the standard library. PR #162927 stabilizes
ptr::cast_slice, the const method that turns a pointer and a length into a slice pointer, on *const T, *mut T and NonNull<T> 34.PR #163458 stabilizes
Rc::is_unique and Arc::is_unique, and PR #163816 stabilizes String::into_chars 3536. None of the three is in a released toolchain yet.The
Rc/Arc deref discussion has a second attempt. PR #132553 sits at 187 comments, last touched October 21, and a newer PR #141348 pursues the same zero-cost Rc<T>::deref goal, at 126 comments on October 24 3738.The leader is unchanged. PR #112049, the CI experiments thread, holds 2,466 comments and last moved on October 21 39.
Two performance discussions moved further. PR #159378, on lexing with a flat token stream, reached 168 comments on October 25, and PR #156496, on splitting the
Components iterator, 107 on October 19 4041.- Why included now: No release, and the work closest to changing how compiled code performs — the zero-cost
derefdiscussion — gained a second pull request. - Upgrade call — Hold:
1.99.1remains the newest stable, and nothing this week changes a toolchain already on it.
Loading content card…
Tailwind CSS
tailwindlabs/tailwindcss published no release.
v4.3.3 from July 16 is still the newest stable 42, and npm's latest tag still points at it 43.Three commits landed on
main. PR #20593 narrows the canonicaliser so it ignores a --tw-{property} variable only next to the property that variable belongs to 44.PR #20591 decodes single-digit hexadecimal CSS escapes, and the third commit only adds the changelog line for it 45.
A stable is still staged. PR #20447, titled "4.3.4", has been open since August 31 and last moved on October 13; nothing has been tagged from it 46.
Twenty-four open issues and pull requests were touched during the week, across the Vite and PostCSS plugins, the scanner and the Windows binaries. PR #20503 stops the Vite plugin retaining a finished build's plugin context 47.
PR #20395 fixes the PostCSS plugin losing watch dependencies after a compile error, and PR #20585 keeps floating-point noise out of constant-folded
calc() and unit conversion 4849.PR #20598 keeps
@keyframes rules that an animation-name refers to, and PR #20524 makes the source scanner respect git's global ignore file 5051.The comment leaders hold: #17958 at 38 comments on the missing
lightningcss.linux-x64-musl.node, #15005 at 33 on @property inside shadow roots, and #17246 at 27 on --watch pinning two cores 525354.- Why included now: Three commits and an open release pull request — there is nothing to install, and the work queued for
4.3.4is mostly integration fixes. - Upgrade call — Hold:
v4.3.3remains the newest stable. If a Vite or PostCSS watch bug is biting you, the fix is onmain.
Quick reference
| Repository | Latest relevant release | Window status and hot watch | Upgrade call |
|---|---|---|---|
| vercel/next.js | 16.4.3, Oct 23 2 | Backport release: font URLs, proxy.ts runtime, a Turbopack revert, OpenTelemetry traces, standalone React in the server bootstrap; <Link prefetch="navigation"> on canary only 5; #49279 has 145 comments and #53473 79 68 | Yes |
| microsoft/vscode | 1.143.0, Oct 22, and 1.143.1 the same night 1 | Copilot harness now the default for new sessions; managed model defaults override chat.defaultModel; compare models preview; on-device models need a 96 GB NVIDIA GPU; diagnostics highlight limit raised to 5,000 12 | Conditional |
| react/react | 19.3.1, Oct 14 20 | No release; eight main commits on Fizz prerendering, resumeAndPrerender and the compiler; #13991 has 515 comments and did not move 28 | Hold |
| rust-lang/rust | 1.99.1, Oct 16 33 | No release; 632 commits; ptr::cast_slice, Rc::is_unique, Arc::is_unique and String::into_chars stabilized on main, none released; second zero-cost deref pull request at 126 comments 38 | Hold |
| tailwindlabs/tailwindcss | v4.3.3, Jul 16 42 | No release; three commits, two of them canonicalisation and escape decoding; 24 open threads moved, led by Vite and PostCSS watch fixes; 4.3.4 PR still open 46 | Hold |
References
- 1Visual Studio Code 1.143.0 release
github.com
- 2Next.js v16.4.3 release
github.com
- 3Next.js v16.5.0-canary.18 release
github.com
- 4Next.js v16.5.0-canary.27 release
github.com
- 5Next.js pull request #99871
github.com
- 6Next.js issue #49279
github.com
- 7Next.js issue #64921
github.com
- 8Next.js issue #53473
github.com
- 9Next.js issue #91396
github.com
- 10Visual Studio Code 1.143.1 release
github.com
- 11VS Code pull request #343541
github.com
- 12Visual Studio Code 1.143 update notes
code.visualstudio.com
- 13VS Code issue #519
github.com
- 14VS Code issue #3130
github.com
- 15VS Code issue #13960
github.com
- 16VS Code issue #4490
github.com
- 17VS Code issue #43188
github.com
- 18VS Code issue #339363
github.com
- 19VS Code issue #5595
github.com
- 20React v19.3.1 release
github.com
- 21React pull request #37916
github.com
- 22React pull request #37901
github.com
- 23React pull request #37853
github.com
- 24React pull request #37876
github.com
- 25React pull request #37856
github.com
- 26React pull request #37975
github.com
- 27React pull request #37895
github.com
- 28React issue #13991
github.com
- 29React issue #11347
github.com
- 30React issue #32950
github.com
- 31React issue #26608
github.com
- 32React issue #34045
github.com
- 33Rust 1.99.1 release
github.com
- 34Rust pull request #162927
github.com
- 35Rust pull request #163458
github.com
- 36Rust pull request #163816
github.com
- 37Rust pull request #132553
github.com
- 38Rust pull request #141348
github.com
- 39Rust pull request #112049
github.com
- 40Rust pull request #159378
github.com
- 41Rust pull request #156496
github.com
- 42Tailwind CSS v4.3.3 release
github.com
- 43npm registry: tailwindcss dist-tags
registry.npmjs.org
- 44Tailwind CSS pull request #20593
github.com
- 45Tailwind CSS pull request #20591
github.com
- 46Tailwind CSS pull request #20447
github.com
- 47Tailwind CSS pull request #20503
github.com
- 48Tailwind CSS pull request #20395
github.com
- 49Tailwind CSS pull request #20585
github.com
- 50Tailwind CSS pull request #20598
github.com
- 51Tailwind CSS pull request #20524
github.com
- 52Tailwind CSS issue #17958
github.com
- 53Tailwind CSS issue #15005
github.com
- 54Tailwind CSS issue #17246
github.com
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.