Starred repos weekly — Jun 2–8, 2026

One release this week worth shipping. Four repos are holding at their May versions — here's the full picture.

Released Jun 5. The headline is Copilot-related infrastructure, but there's useful non-AI stuff too.

Session sync + /chronicle: Chat sessions now sync to your GitHub account and are searchable across machines. The /chronicle command lets you query that history in natural language — "what was I working on last Thursday" or "generate a standup summary." Useful if you context-switch across repos often.

1 million token context window for compatible Anthropic and OpenAI models (Claude Opus 4.7, GPT-5.5). More context consumed per turn, so watch your AI credits.

Research agent (preview, Insiders only): /research in a Copilot CLI local session generates a cited Markdown report from your codebase, linked GitHub repos, and the web. Read-only; doesn't touch your code.

Agent window (preview): A companion window for multi-session agent work. You can open multiple sessions side-by-side, lock ones you want to keep visible, and maximize a single session without closing others.

Delayed extension auto-updates: Extensions from non-trusted publishers now wait 2 hours before auto-applying updates. Microsoft, GitHub, and OpenAI extensions update immediately as before. A small but sensible supply-chain hygiene change.

Integrated browser: address bar now supports bookmarked pages; new area-screenshot and full-page-screenshot options for attaching to chat context.

Full release notes: code.visualstudio.com/updates/v1_123

Hot issue this week: #253124 — "Meta: Request rate limiting" and #253137 — "Meta: Language Model Unavailable" are both open. Copilot rate-limit complaints spiked in the last two weeks — worth tracking if you're on a shared team plan.

Upgrade call: Yes — no breaking changes, and the session sync + delayed auto-update changes are worth having.

v16.2.7 shipped Jun 1 (just before this window) with backported bug fixes: dev-mode hydration failure when served from HTTP cache, router.query corruption with basePath + rewrites, server action forwarding loops with middleware rewrites, and a FormData entries drop fix.

No new stable release this week. Canary reached v16.3.0-canary.44 (Jun 7), focused on Turbopack memory eviction experiments.

Hot issue: #54708 — "Next.js development high memory usage" stays at the top of the most-commented list. The Turbopack eviction work in canary is likely related, but nothing has landed in stable yet.

Upgrade call: Conditional — if you hit the hydration-from-cache or middleware rewrites bugs, v16.2.7 is worth taking. Otherwise stable users can wait for 16.3.

v19.2.7 released Jun 1 (just outside the window) with a single fix: missing FormData entries in Server Actions, a regression from 19.2.6. Same patch applied to 19.1.8 and 19.0.7 simultaneously.

No new release this week.

Hot issue: #11347 — "RFC: Plan for custom element attributes/properties in React 19" remains the most-discussed open thread. Custom element attribute handling has been a long-running pain point; worth watching if you're building web components.

Upgrade call: Yes (if you're on 19.2.6/19.1.7/19.0.6) — the FormData regression is a real correctness issue in server-side forms. Otherwise hold.

1.96.0 (May 28) was covered last week. No release this week.

The most-discussed open thread is #35121 — "Tracking issue for promoting ! (never type) to a full type (RFC 1216)", a multi-year tracking issue that's seen renewed activity. Also watch #31844 — "Tracking issue for specialization (RFC 1210)", still open after years.

Upgrade call: Hold — 1.96.0 is the current stable. Next release (1.97) expected ~Jul 2026.

v4.3.0 (May 8) remains current. No release this week.

#17958 — "Cannot find module '../lightningcss.linux-x64-musl.node'" is still the most-discussed open issue — the musl binary problem affects Alpine/Docker builds. No fix in the last two weeks. If you're building in musl environments, the tailwindcss-v4-alpine workaround or pinning to the prior binary still applies.

Hot second: #16531 — "hover in v4 relies on a buggy Chromium feature" — v4's hover implementation triggers on touch devices in ways v3 didn't. A fix is in progress upstream.

Upgrade call: Hold for musl/Alpine users until #17958 is resolved. Otherwise v4.3.0 is stable.