Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency form-data-encoder to v4 #502

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 18, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
form-data-encoder ^1.7.2 -> ^4.0.0 age adoption passing confidence

Release Notes

octet-stream/form-data-encoder (form-data-encoder)

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

v3.0.1: 3.0.1

Compare Source

Update
  • Fix FormDataLike types compatibility with undici (#​19);
  • Set compilerOptions.module value to node16 to meet TS requirements;

All changes: octet-stream/form-data-encoder@v3.0.0...v3.0.1

v3.0.0: 3.0.0

Compare Source

Remove
  • Remove deprecated isFileLike() utility, use isFile() instead;
  • Remove deprecated FormDataEncoder.getContentLength() method.
Update
  • BREAKING: Drop Node 14.x support. Since 3.x the minimal required version is 16.5.x;
  • Implement internal chunk utility to split value into chunks, if the value size is greater than 65536 bytes. This applied both to Files and string values, because FormDataEnocder supports AsyncIterable returned by File.stream();
  • Expose package.json in esports field of package.json.

All changes: octet-stream/form-data-encoder@v2.1.4...v3.0.0

v2.1.4: 2.1.4

Compare Source

Update
  • Fix for browser compatibility: Add a fallback for ReadableStream that does not implement Symbol.asyncIterator method;
  • Improve documentation for FormDataEncoder constructor.

All changes: octet-stream/form-data-encoder@v2.1.3...v2.1.4

v2.1.3: 2.1.3

Compare Source

Update
  • Replace LowercaseObjectKeys TS utility with two interfaces: RawHeaders and FormDataEncoderHeaders. This should resolve #​8;

All changes: octet-stream/form-data-encoder@v2.1.2...v2.1.3

v2.1.2: 2.1.2

Compare Source

Update

All changes: octet-stream/form-data-encoder@v2.1.1...v2.1.2

v2.1.1: 2.1.1

Compare Source

Update
  • Fix typings exports in package.json

All changes: octet-stream/form-data-encoder@v2.1.0...v2.1.1

v2.1.0: 2.1.0

Compare Source

Update
  • Fix a bug with NaN returned as Content-Length value when FormDataEncoder discovers entries without known length.

All changes: octet-stream/form-data-encoder@v2.0.1...v2.1.0

v2.0.1: 2.0.1

Compare Source

Update
  • Adjust minimal required Node.js version to 14.17

All changes: octet-stream/form-data-encoder@v2.0.0...v2.0.1

v2.0.0: 2.0.0

Compare Source

Breaking
  • Drop CommonJS support. The package is now ESM only;
  • Remove Encoder from exports;
  • Remove deprecated isFormDataLike helper. Use isFormData instead.
Update
  • Minimal required Node.js version is 14.18;
  • Headers in FormDataEncoder.headers property can be accessed in case-insensitive manner. TypeScript users still have correct TS typings, but only for original and lowercased keys (for example Content-Type and content-type);
  • FormData instance will be preserved in array inside of FormDataEncoder instance (previously it held a reference to given FormData instance);
  • Deprecate isFileLike helper. Use isFile instead;
  • Deprecate FormDataEncoder.getContentLength() method. The content-length is now static value, so this method makes no sense. Use FormDataEncoder.contentLength or FormDataEncoder.headers["content-length"] instead.
Add
  • Expose FormDataEncoderHeaders type.

All changes: octet-stream/form-data-encoder@v1.7.2...v2.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

socket-security bot commented Mar 18, 2024

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/form-data-encoder@4.0.2 None 0 59.7 kB octetstream

View full report↗︎

Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.07%. Comparing base (49039b6) to head (7b900e8).
Report is 2 commits behind head on master.

❗ Current head 7b900e8 differs from pull request most recent head 1950b4a. Consider uploading reports for the commit 1950b4a to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #502      +/-   ##
==========================================
- Coverage   98.81%   98.07%   -0.75%     
==========================================
  Files          10       10              
  Lines        1608     1610       +2     
  Branches      269      256      -13     
==========================================
- Hits         1589     1579      -10     
- Misses         19       31      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/form-data-encoder-4.x branch from c740a96 to 8765123 Compare March 18, 2024 05:09
Copy link
Member

@fengmk2 fengmk2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still support node.js 14 on v3

@renovate renovate bot force-pushed the renovate/form-data-encoder-4.x branch from 8765123 to 7b900e8 Compare April 22, 2024 07:00
Copy link

coderabbitai bot commented Apr 22, 2024

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/form-data-encoder-4.x branch from 7b900e8 to 1950b4a Compare April 22, 2024 07:03
@renovate renovate bot force-pushed the renovate/form-data-encoder-4.x branch from 1950b4a to ecdb2cc Compare May 7, 2024 03:55
@fengmk2 fengmk2 closed this May 7, 2024
Copy link
Contributor Author

renovate bot commented May 7, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/form-data-encoder-4.x branch May 7, 2024 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant