Starred repos weekly — Jun 9–15, 2026

Starred repos weekly — Jun 9–15, 2026

VS Code 1.124 ships a rebuilt Agents window, session navigation, and Autopilot on by default — upgrade now. Tailwind v4.3.1 fixes Node 26 deprecations, @apply in mixins, and ~20 other bugs (skip if musl/Alpine). Next.js, React, and Rust all hold at their prior stable releases.

What's New in the Repos I Starred
What's New in the Repos I Starred@NeoDrop Official
2026/6/15 · 17:06
購読 1 件 · コンテンツ 4 件
VS Code 1.124 ships this week with a rebuilt Agents window and Autopilot on by default. Tailwind v4.3.1 quietly lands 20-plus bug fixes. The other three repos hold at their prior stable releases — here's where each stands and whether you should move.

VS Code — 1.124.2 (Jun 12) ✅ Upgrade

microsoft/vscode — the source-code editor (186k ⭐)
1.124 is a focused agentic-workflow release. If you use Copilot in VS Code, this one matters.
Agents window overhaul: the companion window for working across many simultaneous Copilot sessions now restores your layout on reload (visible sessions, their order, pinned/read status), so reopening VS Code doesn't scatter your context. You can open a new background session with Alt+Enter without losing your current one, and jump between sessions with Ctrl+R (a searchable Quick Pick), Ctrl+Tab / Shift+Tab (most-recently-visited order), or Ctrl+1–9 (by grid position). 1
Autopilot is now on by default: Autopilot — the permission level that lets agents act without per-step approval — is enabled for all users. Organizations can still lock it via chat.tools.global.autoApprove. The companion feature, Advanced Autopilot (chat.autopilot.advanced.enabled), swaps the fixed completion rules for a small utility model that reads the chat transcript and decides whether the task is actually done, then surfaces its current objective in a tooltip above the chat. It loops at most three times before stopping.
Integrated browser improvements: the browser now retains a visit history, surfaced as URL-bar suggestions (Ctrl+H to manage). Agents can type and submit text in one typeInPage tool call instead of two, halving round-trips for form automation.
Patch releases 1.124.1 and 1.124.2 closed additional regressions in the same cycle. 1
Hot issues: #253136 (Meta: chat request failures) and #253137 (Language Model Unavailable) are the current tracking issues for Copilot connectivity errors — useful if agents misbehave after the Autopilot default flip.
Upgrade risk: Low. No removed APIs; the Autopilot default change is behavioral, not a breaking code change. Orgs managing Copilot access should review chat.tools.global.autoApprove before rolling out.
コンテンツカードを読み込んでいます…

Next.js — canary v16.3.0 active, stable holds ⏸ Hold

vercel/next.js — the React framework (140k ⭐)
The latest npm tag now points to v16.2.9 (Jun 10), but that release is an empty version published solely to correct a dist-tag mistake — it contains no code changes. 2 The last real stable release remains v16.2.7.
The more significant activity this week was the opening of the v16.3.0 preview channel: v16.3.0-preview.0 through .3 landed Jun 9–10, and canary builds ran to .51 by Jun 14. Preview highlights include stabilizing export const prefetch (removes the unstable_ prefix), enabling Turbopack filesystem caching by default in non-stable releases, and renaming the force-runtime prefetch option to allow-runtime. This is a forward-looking look at what 16.3.0 stable will carry, not something to deploy to production yet. 3
Hot issues: #54708 (High memory usage in development) continues to draw the most comments. #86577 (cacheComponents/Activity component breaking app logic) is the current heat-spot for anyone experimenting with the cacheComponents experimental flag. 4
Upgrade risk: N/A. No stable change. If you're on v16.2.x, stay there; v16.3.0 is not yet stable.

React — v19.2.7 (Jun 1), no new release ⏸ Hold

facebook/react — the UI library (246k ⭐)
No React releases landed in the Jun 9–15 window. The last batch — v19.2.7, v19.1.8, and v19.0.7 — shipped Jun 1 with a single fix: a missing FormData entries regression in Server Actions introduced in the .6 patch series. If you were on any .6 release and haven't moved, those fixes are the reason to upgrade. 5
Hot issues: #13991 (Hooks + multiple React instances) remains the long-running top thread. More practically relevant: #29034 (React 19 — opt out of automatic form reset on Form Actions) is active, if you're using the new form actions API and find the default reset behavior surprising. 6
Upgrade risk: N/A this week. If on 19.x.6, upgrade to .7. If already on .7, hold.
コンテンツカードを読み込んでいます…

Rust — 1.96.0 (May 28), stable until ~Jul 2026 ⏸ Hold

rust-lang/rust — the Rust programming language (114k ⭐)
No new Rust release this week. 1.96.0, which shipped May 28, remains current. Key points from that release worth recapping: assert_matches! and debug_assert_matches! are now stable; six new core::range::* types landed (including Range, RangeFrom, RangeToInclusive and their iterator variants); Cargo patched CVE-2026-5222 and CVE-2026-5223. The next stable release is expected around early July 2026. 7
Hot issues: The ongoing CI experiments PR #112049 and -Znext-solver experiments #133502 top the comments list but are internal infrastructure probes marked "do not merge." More user-relevant: allocator traits tracking #32838 — the custom allocator API is still evolving if your project depends on std::alloc. 8
Upgrade risk: Low if still on 1.95.x — 1.96.0 ships several compatibility notes (enum layout changes, wasm --allow-undefined removed, $crate self-import restriction). Review the compatibility notes before upgrading in CI.

Tailwind CSS — v4.3.1 (Jun 12) ✅ Upgrade (conditional)

tailwindlabs/tailwindcss — utility-first CSS framework (95.6k ⭐)
v4.3.1 is a pure bug-fix patch over v4.3.0, landing Jun 12 with around 20 fixes. The ones most likely to affect real projects:
  • Node 26: uses Module#registerHooks instead of the deprecated Module#register, removing the deprecation warnings Node 26 started emitting. 9
  • @apply with CSS mixins now works where it was previously blocked.
  • not-* variants correctly negate @container queries including style(…) queries.
  • Rspack: @tailwindcss/webpack can now be installed in Rspack projects without requiring webpack as a peer dependency.
  • Symlink scanning: @source globs with symlinks are now preserved; explicitly referenced @source directories are scanned even when git-ignored.
  • Spacing output: m-0 now emits 0 instead of calc(var(--spacing) * 0), and m-1 emits var(--spacing) instead of calc(var(--spacing) * 1) — smaller, cleaner output.
Still open: #17958 — lightningcss.linux-x64-musl.node module not found — affects Alpine Linux / Docker musl environments and is blocked on an upstream fix. If you build in musl containers, stay on v4.3.0 or pin a workaround.
Hot issues: #15005 (@property unsupported in shadow roots) and #15045 (addComponents writing to @layer utilities instead of @layer components) are the two most discussed open threads.
Upgrade risk: Low for non-musl environments. Drop-in upgrade from v4.3.0.
コンテンツカードを読み込んでいます…

Quick-reference table

RepoLatest stableReleasedUpgrade call
microsoft/vscode1.124.2Jun 12✅ Yes
vercel/next.js16.2.7 (stable)Jun 1⏸ Hold (16.2.9 is a dist-tag-only release)
facebook/react19.2.7Jun 1⏸ Hold (if on .7 already)
rust-lang/rust1.96.0May 28⏸ Hold (next release ~Jul 2026)
tailwindlabs/tailwindcss4.3.1Jun 12✅ Yes (skip if musl/Alpine)

参考ソース

  1. 1VS Code 1.124 release notes
  2. 2Next.js v16.2.9 release
  3. 3Next.js v16.3.0-preview.0
  4. 4Next.js issues
  5. 5React v19.2.7 release
  6. 6React issues
  7. 7Rust 1.96.0 release
  8. 8Rust issues
  9. 9Tailwind v4.3.1 release
What's New in the Repos I Starred
What's New in the Repos I Starred

このコンテンツについて、さらに観点や背景を補足しましょう。

  • ログインするとコメントできます。