chore(security): bumping effect to 3.20.0 because of GHSA-38f7-945m-qr2g#1276
chore(security): bumping effect to 3.20.0 because of GHSA-38f7-945m-qr2g#1276tnovau wants to merge 1 commit intopingdotgg:mainfrom
Conversation
|
|
@tnovau is attempting to deploy a commit to the Ping Labs Team on Vercel. A member of the Team first needs to authorize it. |
Greptile SummaryThis PR bumps Confidence Score: 5/5Safe to merge — clean security patch with only expected lockfile drift as a side effect. All package.json files consistently update effect to 3.20.0. The pnpm lockfile correctly reflects these updates. The Next.js canary version bump in the lockfile is expected behavior caused by the floating "canary" specifier in the playground packages and does not affect any published packages. No logic changes are introduced. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["GHSA-38f7-945m-qr2g\n(Security Advisory)"] --> B["effect 3.17.7 → 3.20.0"]
B --> C["packages/shared"]
B --> D["packages/uploadthing"]
B --> E["examples/backend-adapters/server"]
B --> F["playground"]
B --> G["playground-v6"]
B --> H["tooling/tsconfig"]
F -->|floating 'canary' specifier| I["pnpm-lock.yaml\nNext.js 15.4.2-canary.51\n→ 16.2.1-canary.43\n(side effect)"]
G -->|floating 'canary' specifier| I
Reviews (1): Last reviewed commit: "chore: bumping effect to 3.20.0 because ..." | Re-trigger Greptile |
WalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This PR attemps to fix a high security issue described on GHSA-38f7-945m-qr2g that's related to
effectnpm package that's widely used in this repo.Summary by CodeRabbit