TimMikeladze / next-upload

🗃️ Turn-key solution for signed & secure file-uploads to an S3 compliant storage service such as R2, AWS, or Minio. Built for Next.js. Generates signed URLs for uploading files directly to your storage service and optionally integrates with a database to store additional metadata about your files.
MIT License
83 stars 4 forks source link

chore(deps): bump wrangler from 3.17.1 to 3.22.2 #33

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

Bumps wrangler from 3.17.1 to 3.22.2.

Release notes

Sourced from wrangler's releases.

wrangler@3.22.2

Patch Changes

  • #4600 4233e514 Thanks @​mrbbot! - fix: apply source mapping to deployment validation errors

    Previously if a Worker failed validation during wrangler deploy, the displayed error would reference locations in built JavaScript files. This made it more difficult to debug validation errors. This change ensures these errors are now source mapped, referencing locations in source files instead.

  • #4440 15717333 Thanks @​mrbbot! - fix: automatically create required directories for wrangler r2 object get

    Previously, if you tried to use wrangler r2 object get with an object name containing a / or used the --file flag with a path containing a /, and the specified directory didn't exist, Wrangler would throw an ENOENT error. This change ensures Wrangler automatically creates required parent directories if they don't exist.

  • #4592 20da658e Thanks @​mrbbot! - fix: throw helpful error if email validation required

    Previously, Wrangler would display the raw API error message and code if email validation was required during wrangler deploy. This change ensures a helpful error message is displayed instead, prompting users to check their emails or visit the dashboard for a verification link.

  • #4597 e1d50407 Thanks @​mrbbot! - fix: suggest checking permissions on authentication error with API token set

  • #4593 c370026d Thanks @​mrbbot! - fix: include messages from API in errors

  • #4588 4e5ed0b2 Thanks @​mrbbot! - fix: require worker name for rollback

    Previously, Wrangler would fail with a cryptic error if you tried to run wrangler rollback outside of a directory containing a Wrangler configuration file with a name defined. This change validates that a worker name is defined, and allows you to set it from the command line using the --name flag.

  • Updated dependencies [c410ea14]:

    • miniflare@3.20231218.0

wrangler@3.22.1

Patch Changes

  • #4635 5bc2699d Thanks @​mrbbot! - fix: prevent zombie workerd processes

    Previously, running wrangler dev would leave behind "zombie" workerd processes. These processes prevented the same port being bound if wrangler dev was restarted and sometimes consumed lots of CPU time. This change ensures all workerd processes are killed when wrangler dev is shutdown.

    To clean-up existing zombie processes, run pkill -KILL workerd on macOS/Linux or taskkill /f /im workerd.exe on Windows.

wrangler@3.22.0

Minor Changes

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.22.2

Patch Changes

  • #4600 4233e514 Thanks @​mrbbot! - fix: apply source mapping to deployment validation errors

    Previously if a Worker failed validation during wrangler deploy, the displayed error would reference locations in built JavaScript files. This made it more difficult to debug validation errors. This change ensures these errors are now source mapped, referencing locations in source files instead.

  • #4440 15717333 Thanks @​mrbbot! - fix: automatically create required directories for wrangler r2 object get

    Previously, if you tried to use wrangler r2 object get with an object name containing a / or used the --file flag with a path containing a /, and the specified directory didn't exist, Wrangler would throw an ENOENT error. This change ensures Wrangler automatically creates required parent directories if they don't exist.

  • #4592 20da658e Thanks @​mrbbot! - fix: throw helpful error if email validation required

    Previously, Wrangler would display the raw API error message and code if email validation was required during wrangler deploy. This change ensures a helpful error message is displayed instead, prompting users to check their emails or visit the dashboard for a verification link.

  • #4588 4e5ed0b2 Thanks @​mrbbot! - fix: require worker name for rollback

    Previously, Wrangler would fail with a cryptic error if you tried to run wrangler rollback outside of a directory containing a Wrangler configuration file with a name defined. This change validates that a worker name is defined, and allows you to set it from the command line using the --name flag.

  • Updated dependencies [c410ea14]:

    • miniflare@3.20231218.0

3.22.1

Patch Changes

  • #4635 5bc2699d Thanks @​mrbbot! - fix: prevent zombie workerd processes

    Previously, running wrangler dev would leave behind "zombie" workerd processes. These processes prevented the same port being bound if wrangler dev was restarted and sometimes consumed lots of CPU time. This change ensures all workerd processes are killed when wrangler dev is shutdown.

    To clean-up existing zombie processes, run pkill -KILL workerd on macOS/Linux or taskkill /f /im workerd.exe on Windows.

3.22.0

Minor Changes

  • #4632 a6a4e8a4 Thanks @​G4brym! - Deprecate constellation commands and add a warning when using the constellation binding

3.21.0

... (truncated)

Commits
  • 259b5a6 Version Packages (#4655)
  • 4233e51 [wrangler] fix: apply source mapping to deployment validation errors (#4600)
  • 20da658 fix: throw helpful error if email validation required (#4592)
  • c370026 fix: include messages from API in errors (#4593)
  • e1d5040 [wrangler] fix: check permissions on authentication error with API token set ...
  • 1571733 fix: create required parent directories for wrangler r2 object get (#4440)
  • 0f424cf Fix help message for listing scopes (#4647)
  • 4e5ed0b fix: require worker name for rollback (#4588)
  • 6d3d46a Version Packages (#4638)
  • 5bc2699 fix: prevent zombie workerd processes (#4635)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/TimMikeladze/next-upload/network/alerts).
dependabot[bot] commented 5 months ago

Superseded by #35.