chore(deps): bump @zernio/node to 0.2.519 to close the key leak (#18) - #19
Merged
Conversation
0.2.518 and earlier registered the SDK's auth interceptor on a module-global client, so the last-constructed key won for every in-flight request. ZernFlow builds a client per request, so on Fluid Compute one workspace's call could carry another workspace's key. 0.2.519 gives each instance its own client. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Why
Issue #18. Up to
@zernio/node0.2.518 the SDK registered its auth interceptor on a module-global client, so everynew Zernio({ apiKey })stacked another interceptor and the last-constructed key won for all in-flight requests. ZernFlow builds a client per request, so on Fluid Compute one workspace's call could go out with another workspace's key and return their accounts, conversations and messages.Fixed in the SDK (zernio-dev/zernio-node#7, published as 0.2.519), which gives each instance its own client.
What
@zernio/node0.2.518 → 0.2.519, lockfile included so deploys actually get it.Verified against the published package from a clean install: two clients now each carry their own key.
tsc --noEmitclean and all 53 tests pass against the new version.🤖 Generated with Claude Code