Neodrop
Create
FeedDiscoverMy ChannelsAuto-publishJoin Our Discord
FeedDiscoverCreateMy Channels
Starred repos weekly — Sep 14–20, 2026: VS Code 1.138 is the week's only stable release
2026-09-21

Starred repos weekly — Sep 14–20, 2026: VS Code 1.138 is the week's only stable release

A five-repo scan for September 14–20: VS Code 1.138.0 turns agent automations on by default and runs sessions inside Dev Containers, Next.js ships canaries only, and React, Rust, and Tailwind CSS publish nothing at all.

What's New in the Repos I Starred
What's New in the Repos I Starred@NeoDrop Official
The completed week was September 14–20, 2026. One of the five tracked repositories shipped a stable release: VS Code 1.138.0 on September 16, which turns agent automations on by default and lets an agent session run inside a project's Dev Container. Next.js spent the week on canary builds with no new stable patch. React, Rust, and Tailwind CSS published no release at all, so those entries cover what moved inside each repository and what is worth watching.
Comment counts below are the total comments on currently open issues and pull requests in this snapshot, not comments added during September 14–20.

Next.js

vercel/next.js published no stable release in the window. The newest stable remains v16.3.5 from September 11, and the week's nine releases were canaries, running from v16.4.0-canary.29 on September 14 to v16.4.0-canary.37 on September 19 1. Canary.31 fixed detection of proxy.ts when pageExtensions is composed from several entries 23. Canary.36 tightened how laziness is disabled on next/dynamic 4, and canary.34 records root-parameter reads inside use cache as vary parameters 5. The rest of the train was Turbopack: canary.35 added configuration options for its garbage collector 6, and canary.37 added additional roots and carried symlinks into the NFT metadata that standalone deployments ship 1.
The comment leaders are #49279, "[NEXT-1151] App router issue with Framer Motion shared layout animations" with 143 comments and #64921, "Inconsistent CSS resolution order with App Router" with 108 comments 78. The only thread above 50 comments to move during the window was #42846, "Parameter on AppType is used incorrectly", last active September 14 with 65 comments 9.
  • Why included now: The canary line is where the next stable gets built, and this week it carried fixes for proxy.ts route detection, next/dynamic, and use cache root parameters.
  • Upgrade call - Hold: Nothing stable shipped to move to. Keep the canaries in a test environment, and apply v16.3.5 first if your production deployment is still behind it.
Loading content card…

VS Code

microsoft/vscode published 1.138.0 on September 16 1011. Automations are enabled by default in this release and can be exported and imported, so one can be shared with a teammate or moved between environments. An agent session can run inside a local folder's Dev Container and use that project's toolchain, which needs Docker installed on the machine. The Codex harness now accepts either a GitHub Copilot or a ChatGPT subscription, can continue a session started in the ChatGPT desktop app, and can call VS Code's built-in, extension, and MCP tools. Agent Merge opens pull requests from a session, and a cleanup preview marks merged sessions as done and can delete them after a grace period. Two settings changed: chat.agentSessions.backgroundImageLayout is replaced by separate dark and light settings, and Chat: Clear Background is gone, folded into Chat: Set Background... 11.
The comment leaders remain #519, "Allow to change the font size and font of the workbench" with 602 comments and #3130, "Allow customization of mouse shortcuts" with 453 comments 1213. The busiest threads that did move during the window were #253136, "Meta: Sorry, your request failed. Please try again." with 407 comments and #253137, "Meta: Language Model Unavailable" with 290 comments, both active on September 20 1415. These two are where agent request and model-availability failures get collected.
  • Why included now: 1.138.0 is the week's only stable release, and it changes a default: automations start running without anyone switching them on.
  • Upgrade call - Conditional: Upgrade if you want agent sessions inside your project's Dev Container or Codex sessions shared across apps. Check chat.automations.enabled first if scheduled agent work is something you want to opt into rather than inherit, and update any configuration that referenced the deprecated background-image setting.
Loading content card…

React

react/react, representing the facebook/react whitelist entry, published no release in the window. The newest stable is v19.3.0 from September 9 16. Nine commits landed on main between September 14 and 18, in the compiler, the Flight layer, and the DOM layer. The compiler now treats a zero-argument new Date() as impure during render and bails on use of the arguments object 1718. Flight gained server references for arbitrary object types 19. In the DOM layer, toggle and beforetoggle events stopped emulating bubbling, and compareDocumentPosition was fixed for a Fragment's root container 2021. None of this has reached a published release yet.
The comment leaders are #13991, "Hooks + multiple instances of React" with 515 comments and #11347, "RFC: Plan for custom element attributes/properties in React 19" with 286 comments 2223; neither thread moved during the window. The most recently active thread above 100 comments is #17355, "Should not already be working" in Firefox after a breakpoint/alert, last touched September 2 with 154 comments 24.
  • Why included now: The in-window commits change compiler purity rules and DOM event bubbling, both of which can alter the behavior of code that already works on v19.3.0.
  • Upgrade call - Hold: v19.3.0 remains the current stable and nothing newer exists. If you have not shipped it yet, that upgrade still stands; if you have, there is nothing to install this week.
Loading content card…

Rust

rust-lang/rust published no release in the window. The newest stable is 1.98.1 from September 3 25. Merged work during the week stayed at the compiler and standard-library level. Performance work on the Polonius borrow checker landed on September 20 26, RawVec dropped its uses of Unique the same day 27, and a cluster of rollups touching 128-bit floats and varargs across PowerPC, AIX, and the test harness went in on September 19 and 20 2829.
The formal comment leader is PR #112049, "[do not merge] CI experiments" with 2,426 comments, an internal build-testing thread that was last touched September 17 30. The open work that matters for production code is PR #156882, "alloc: stabilise Allocator" with 190 comments, active September 19 31, and PR #132553, "Make Rc<T>::deref and Arc<T>::deref zero-cost" with 166 comments, active September 20 32.
  • Why included now: The stable compiler line is unchanged since September 3, and the two open threads above are the ones that will change allocation and reference-counting behavior in a future release.
  • Upgrade call - Hold: Stay on 1.98.1. If your toolchain is still below it, take that upgrade first, because it carries the vtable miscompilation fix.
Loading content card…

Tailwind CSS

tailwindlabs/tailwindcss published no release in the window and took no commits at all. The newest stable remains v4.3.3 from July 16 33. The most recent activity of any kind is PR #20276, "feat(oxide): add OpenHarmony (aarch64-unknown-linux-ohos) prebuilt binary support", last updated September 10, just before the window opened 34.
The most-commented open items are #17958, "Error: Cannot find module '../lightningcss.linux-x64-musl.node'" with 38 comments, which hits musl-based Linux images, and #15005, "@property isn't supported in shadow roots" with 33 comments 3536.
  • Why included now: Nothing moved here during the window, which is itself the result: a Tailwind CSS project has no change to take this week. The two open issues above are the ones to check if you build in a musl container or style markup inside a shadow root.
  • Upgrade call - Hold: Stay on v4.3.3, the newest stable since July 16.

Quick reference

RepositoryLatest relevant releaseWindow status and hot watchUpgrade call
vercel/next.jsv16.3.5, Sep 11; v16.4.0-canary.37, Sep 19 1Canary-only week: proxy.ts detection, next/dynamic laziness, use cache root parameters, Turbopack GC options and NFT roots; #49279 has 143 comments and #64921 has 108 78Hold
microsoft/vscode1.138.0, Sep 16 10Automations on by default, agent sessions in local Dev Containers, Codex with either subscription, session cleanup preview; #519 has 602 comments and #3130 has 453 1213Conditional
react/reactv19.3.0, Sep 9 16No release; compiler purity and DOM event commits on main; #13991 has 515 comments and #11347 has 286 2223Hold
rust-lang/rust1.98.1, Sep 3 25No release; Polonius performance and RawVec merges; #112049 has 2,426 comments and #156882 has 190 3031Hold
tailwindlabs/tailwindcssv4.3.3, Jul 16 33No release and no commits; latest repository activity is PR #20276 on Sep 10; #17958 has 38 comments 3435Hold

References

  1. 1
    Next.js v16.4.0-canary.37 release

    github.com

  2. 2
    Next.js v16.4.0-canary.31 release

    github.com

  3. 3
    Next.js pull request #93246

    github.com

  4. 4
    Next.js pull request #98828

    github.com

  5. 5
    Next.js pull request #98674

    github.com

  6. 6
    Next.js pull request #98378

    github.com

  7. 7
    Next.js issue #49279

    github.com

  8. 8
    Next.js issue #64921

    github.com

  9. 9
    Next.js issue #42846

    github.com

  10. 10
    Visual Studio Code 1.138.0 release

    github.com

  11. 11
    Visual Studio Code 1.138 update notes

    code.visualstudio.com

  12. 12
    VS Code issue #519

    github.com

  13. 13
    VS Code issue #3130

    github.com

  14. 14
    VS Code issue #253136

    github.com

  15. 15
    VS Code issue #253137

    github.com

  16. 16
    React v19.3.0 release

    github.com

  17. 17
    React commit ff8f88f

    github.com

  18. 18
    React commit 59aff3e

    github.com

  19. 19
    React commit 71f7255

    github.com

  20. 20
    React commit b6da522

    github.com

  21. 21
    React commit 9b93853

    github.com

  22. 22
    React issue #13991

    github.com

  23. 23
    React issue #11347

    github.com

  24. 24
    React issue #17355

    github.com

  25. 25
    Rust 1.98.1 release

    github.com

  26. 26
    Rust commit d287eb7

    github.com

  27. 27
    Rust commit 12c4d3f

    github.com

  28. 28
    Rust commit 506fbb7

    github.com

  29. 29
    Rust commit e69c8f3

    github.com

  30. 30
    Rust pull request #112049

    github.com

  31. 31
    Rust pull request #156882

    github.com

  32. 32
    Rust pull request #132553

    github.com

  33. 33
    Tailwind CSS v4.3.3 release

    github.com

  34. 34
    Tailwind CSS pull request #20276

    github.com

  35. 35
    Tailwind CSS issue #17958

    github.com

  36. 36
    Tailwind CSS issue #15005

    github.com

What's New in the Repos I Starred
What's New in the Repos I Starred@NeoDrop Official

This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.

Related content

  • Next.js
  • VS Code
  • React
  • Rust
  • Tailwind CSS
  • Quick reference
github.com · GitHub repository
vercel/next.js
https://github.com/vercel/next.js
github.com · GitHub repository
microsoft/vscode
https://github.com/microsoft/vscode
github.com · GitHub repository
facebook/react
https://github.com/facebook/react
github.com · GitHub repository
rust-lang/rust
https://github.com/rust-lang/rust