Weekly package maintenance — 2026-08-18 - #1123
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour. 📝 WalkthroughWalkthroughThe package manifest updates production and development dependency versions. It also updates pnpm overrides for ChangesDependency refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR is limited to dependency declarations and the lockfile, with security audits and validation checks passing; no actionable merge-blocking risk remains beyond normal review. Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
ncucandidates, while keeping every resolved package release older than 24 hoursnanoid@3.3.18anddeepmerge-ts@8.0.1@langchain/coresecurity override to1.2.8forlangchain@1.5.9compatibilityRoot candidates
Updated:
@e2b/code-interpreter@2.7.1,e2b@2.39.0, all direct Trigger.dev packages to4.5.11,@vercel/functions@3.9.3,convex@1.44.0,centrifuge@5.7.1,redis@6.2.1, andws@8.21.3@legendapp/list@3.3.6,@workos-inc/widgets@1.16.1,next/eslint-config-next@16.3.1,posthog-js@1.417.3,react-shiki@0.11.1, andswr@2.5.1@posthog/ai@8.8.0,posthog-node@5.49.1,@workos-inc/node@10.10.0,gpt-tokenizer@4.0.0,jose@6.2.9,langchain@1.5.9, andstripe@22.5.0@posthog/cli@0.11.3,@testing-library/user-event@14.6.4, andconcurrently@10.0.5Skipped:
@ai-sdk/openai@4,@ai-sdk/react@4,@openrouter/ai-sdk-provider@3,ai@7,@workos-inc/authkit-nextjs@4.3.1,chalk@6,openai@7,pdfjs-serverless@1.3.1, and@testing-library/jest-dom@7. CI remains Node 20;aiand AuthKit are locally patched, and PDFJS also retains the known typed-array incompatibility.3.1111.0updates for@aws-sdk/client-lambda-microvms,@aws-sdk/client-s3, and@aws-sdk/s3-request-presignerwere conservatively reverted after six Preview Cloud Agent attempts returned AWSInvalidSignatureException. Production on the3.1107.0baseline completed the same command successfully. The failure persisted on the post-revert Preview deployment, so these candidates remain skipped and the evidence now points to Preview's environment-provided AWS credentials/signing configuration rather than the generated client package.lucide-react,marked, oruuid. Eligible fallback versions were used below the too-new latest releases for Legend List, E2B, PostHog JS/CLI, and Testing Library user-event.@types/node@26,eslint@10,typescript@7, andpnpm@11are intentionally outside dependency maintenance scope.ncualso reported thepnpmpackage-manager candidate in addition to the 46 direct dependency/devDependency candidates.Package-to-feature mapping
Validation
minimumReleaseAge=1440posthog-js@1.417.3at about 27.3 hourspackage.json,git diff --check, lint (7 existing warnings), and TypeScript typecheck passedPreview verification
Browser-plugin Google Chrome verification passed for client navigation/reload, task creation and saved-task/sidebar persistence, streamed response rendering, Markdown table/code/Mermaid output, Legend List message rendering, attachment/access/cloud/model selectors, and Security settings. The exercised task and reload produced no application runtime exception or failed application request; the only reload error was the known Vercel feedback-toolbar root
405, and canceled prefetches werenet::ERR_ABORTED.Cloud Agent execution is blocked in Preview. On rollback deployment
hackerai-hu3fc1n78-hackerai.vercel.app, Trigger runrun_06g1d5av8bletirfatdqqf54e1used worker20260818.2and failed both AWS Lambda MicroVM creation attempts with HTTP 403InvalidSignatureException,credential_source=environment, before the harmless command ran. The task response and failure persisted after reload. This PR remains draft until Preview AWS credentials/signing are repaired and the real Cloud Agent command can be rerun successfully; CodeRabbit has therefore only recorded its expected draft skip, not a full review.Summary by CodeRabbit