chore(deps): remove uuid, use built-in crypto#105
Merged
cacieprins merged 2 commits intomasterfrom Apr 30, 2026
Merged
Conversation
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 70413a9. Configure here.
mschile
approved these changes
Apr 30, 2026
|
🎉 This PR is included in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.

PR checklist
npm testlocally and all tests are passing.Summary
Removes the
uuiddependency and generates UUIDs with Node’s built-incrypto.randomUUID():lib/auth.js):cnoncewhenqopis set — still strips hyphens as before (randomUUID().replace(/-/g, '')).lib/multipart.js): formboundarystring.Breaking / compatibility
package.jsonrequires Node>= 14.17.0(minimum version that providescrypto.randomUUID()).uuidpackage implementation rather than the output shape.Risk note
Medium: Engine requirement is stricter than before, and random values are used for auth and multipart boundaries — worth sanity-checking digest-auth and multipart uploads against real backends if you rely on those paths.