Repository navigation
chore(evi): refresh @vercel/connect lockfile to 2.4.1 - #792
Open
evlogai[bot] wants to merge 1 commit into
Open
evlogai[bot] wants to merge 1 commit into
evlogai[bot] wants to merge 1 commit into
Conversation
2.4.1 raises the @auth/core peer floor to >=0.41.3; no @auth/core is installed in this workspace (the peer was already unmet at 2.4.0) and the dist code is byte-identical to 2.4.0, so this is a lockfile-only move under the existing ^2.3.5-style range, now written as ^2.4.1.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Contributor
|
Thank you for following the naming conventions! 🙏 |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #791 (same lockfile, so it rebases trivially once that lands).
What changed
@vercel/connect2.4.0 → 2.4.1, the only delta between the published releases (tarball diff):peerDependencies['@auth/core']:>=0.37.0→>=0.41.3(devDependency0.37.4→0.41.3).dist/code byte-identical to 2.4.0.The range in
apps/evi/package.jsonis written as^2.4.1(the previous^2.3.5already admitted 2.4.1;pnpm updaterewrote it, which keeps the intent explicit). No@auth/coreis installed anywhere in this workspace, so the raised peer floor is unmet exactly as it was at 2.4.0:pnpm peers checkreports no connect- or auth-related issue, before or after.The public
vercel/vercelmirror froze at 2026-09-08, so the release note for 2.4.1 is not visible; the tarball diff above is the evidence.Checks
From
/workspace/repoon8cc3469, with the remote cache connected:pnpm peers check: no@vercel/connector@auth/corefindings.pnpm run typecheck: 30/30 tasks successful (0 cached).apps/evipnpm test: 43 files, 305 tests passed.No changeset: lockfile plus one dependency range in
apps/evi.ELI5
A dependency the app uses published a tiny patch release that only tightens a recommendation about an optional package the app does not even use; the actual code is unchanged. This pull request just moves the pinned copy to the newest patch and re-runs the tests, which all pass.