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

Update dependency formidable to v3 - autoclosed #1270

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
formidable 2.1.2 -> 3.5.1 age adoption passing confidence

Release Notes

node-formidable/formidable (formidable)

v3.5.1

Compare Source

  • fix: (#​945) multipart parser fix: flush or fail always (don't hang)

v3.5.0

Compare Source

  • feature: (#​944) Dual package: Can be imported as ES module and required as commonjs module

v3.4.0

Compare Source

  • feature: (#​940) form.parse returns a promise if no callback is provided
  • it resolves with an array [fields, files]

v3.3.2

Compare Source

  • feature: (#​855) add options.createDirsFromUploads, see README for usage
  • form.parse is an async function (ignore the promise)
  • benchmarks: add e2e becnhmark with as many request as possible per second
    • npm run to display all the commands
  • mark as latest on npm

v3.2.5

Compare Source

  • fix: (#​881) fail earlier when maxFiles is exceeded

v3.2.4

Compare Source

  • fix: (#​857) improve keep extension
  • The code from before 3.2.4 already removed some characters from the file extension. But not always. So it was inconsistent.
  • The new code cuts the file extension at the first invalid character (invalid in a file extension).
  • The characters that are considered invalid inside a file extension are all except the . numbers and a-Z.
  • This change only has an effect if filename option is not used and keepextension option is used

v3.2.3

Compare Source

  • fix: (#​852) end event is emitted once

v3.2.1

Compare Source

  • fix: do not let empty file on error (#​796)
  • it was probably due to the fact that .destroy on a file stream does not always complete on time

v3.2.0

Compare Source

  • feat: maxFileSize option is now per file (as the name suggests) (#​791)
  • feat: add maxFiles option, default Infinity
  • feat: add maxTotalFileSize, default is maxFileSize (for backwards compatibility)
  • fix: minFileSize is per file
  • fix: allowEmptyFiles fix in cases where one file is not empty
  • fix: allowEmptyFiles false option by default
  • fix: rename wrongly named error
  • refactor: rename wrongly named maxFileSize into maxTotalFileSize

v3.1.5

Compare Source

  • fix: PersistentFile.toString (#​796)

v3.1.4

Compare Source

  • fix: add missing pluginFailed error (#​794)
  • refactor: use explicit node imports (#​786)

v3.1.3

Compare Source


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.

@renovate renovate bot force-pushed the renovate/formidable-3.x branch from 3360527 to 1eb9846 Compare June 17, 2023 10:39
@kethinov kethinov added the breaking Change will require a major version bump label Jun 24, 2023
@renovate renovate bot force-pushed the renovate/formidable-3.x branch 2 times, most recently from 54589b4 to 0dba990 Compare June 28, 2023 23:37
@renovate renovate bot changed the title Update dependency formidable to v3 Update dependency formidable to v3 - autoclosed Nov 10, 2023
@renovate renovate bot closed this Nov 10, 2023
@renovate renovate bot deleted the renovate/formidable-3.x branch November 10, 2023 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Change will require a major version bump
Development

Successfully merging this pull request may close these issues.

1 participant