Repository navigation
Conversation
- next 16.3.3 -> 16.4.1 (website, docs) - vite 8.2.2 -> 8.2.4 (root, web, override) - sharp 0.35.4 -> 0.35.5 (root, override, website) - lock only: dompurify 3.4.14 -> 3.4.17, @modelcontextprotocol/sdk 1.30.0 -> 1.32.2, proxy-addr 2.0.7 -> 2.0.8
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review.
|
chore(sync): reconcile main into dev/v0.16 after the cask promotion
|
@greptileai Review exact head |
[Medium impact] The dependency updates appear safe to merge; no actionable regressions were found.
|
Carries #376 to main: next 16.4.1, vite 8.2.4, sharp 0.35.5, dompurify 3.4.17, the MCP SDK 1.32.2 and proxy-addr 2.0.8. The website and docs deploy from main, so this is what puts the next and dompurify fixes live. Nothing in the npm runtime package changes and no tag follows. Review scope: single-user local desktop app.
🔒 Security
dev/v0.16tomain.proxy-addrto 2.0.8.proxy-addrupdates are lockfile-only. The npm runtime package does not change, and no tag follows.🔧 Changed
Update the Next.js dependency in
apps/docs/package.jsonandapps/website/package.json.Update Vite and Sharp dependency declarations in the web, website, and root package files.
Test status is not provided.