Skip to content

[pull] canary from vercel:canary - #2090

Merged
pull[bot] merged 7 commits into
MLH-Fellowship:canaryfrom
vercel:canary
Sep 28, 2026
Merged

pull[bot] merged 7 commits into
MLH-Fellowship:canaryfrom
vercel:canary

Conversation

@pull

@pull pull Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

devjiwonchoi and others added 7 commits September 28, 2026 08:15
Stacked on #99230.

### Why?

Simplify the advisory check by querying only the versions we need
instead of sending a bulk audit request.

### How?

Query npm advisories for the installed version and relevant upgrade
candidates. Remove the GHSA lookup and fallback. Only show a nudge when
the assessment finds a ready target; otherwise, skip it.

<!-- NEXT_JS_LLM -->

Closes NAR-948
Stacked on #99222.

### Why?

Developers running `next dev` with `agenticAutoUpgrade` enabled need a
browser reminder when their installed Next.js version is affected by a
security advisory.

### How?

Assess upgrades once during dev startup and share the result with the
CLI nudge. The existing HMR `SYNC` message carries the security advisory
to DevTools, which shows a Vulnerability Insight in the existing
Insights overlay with a copyable upgrade prompt.

The Insight applies to the `security`, `latest`, and `future` policies
when the assessment finds an affected version and a safe target. A
private test override previews the UI without a vulnerable fixture or
live advisory data.

### Screenshots

These show the badge and overlay layout. The current copied prompt runs
`next upgrade --ai=security` from the app directory.

**DevTools badge**

![DevTools
badge](https://github.com/user-attachments/assets/d6af6daf-0501-497c-aa3f-fe0f95351bc1)

| Light | Dark |
| --- | --- |
| ![Overlay in light
mode](https://github.com/user-attachments/assets/e7a7e194-0595-41e6-97b6-b54c05c14aa7)
| ![Overlay in dark
mode](https://github.com/user-attachments/assets/1b80b7d7-376b-4883-a8d1-3ee7354c92ab)
|

<!-- NEXT_JS_LLM -->

Closes NAR-939
### Why?

Let users choose whether an upgrade runs in a separate worktree.

### How?

Ask in the existing agent's single upgrade question or before launching
a new agent, then pass the choice into the upgrade instructions.

<!-- NEXT_JS_LLM -->

Closes NAR-947
Stacked on #99232.

### Why?

Let users choose the model and effort for a new upgrade agent.

### How?

Ask for model, then effort, in separate selectors and pass both to the
CLI. Existing agents keep their settings.

<!-- NEXT_JS_LLM -->

Closes NAR-947
Stacked on #99235.

### Why?

Let users choose whether a new upgrade agent uses Auto permissions.

### How?

Ask Yes/No after model and effort. No sets explicit approvals; CLIs
without Auto use a supported approval mode. Existing agents keep their
permissions.

<!-- NEXT_JS_LLM -->

Closes NAR-947
Stacked on #99291.

### Why?

Let users revisit upgrade choices before the new agent starts.

### How?

Use the existing CLI selector with a dim hint above each menu. Esc goes
back to the previous choice, or cancels from the first prompt; Ctrl+C
cancels from any prompt. Remove the Cancel rows.

<!-- NEXT_JS_LLM -->
@pull pull Bot locked and limited conversation to collaborators Sep 28, 2026
@pull pull Bot added the ⤵️ pull label Sep 28, 2026
@pull
pull Bot merged commit 50199e6 into MLH-Fellowship:canary Sep 28, 2026
3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant