Bump the development-dependencies group across 1 directory with 2 updates

[dependabot]

Bumps the development-dependencies group with 2 updates in the /url-unfurler directory: @cloudflare/workers-types and wrangler.

Updates @cloudflare/workers-types from 4.20240405.0 to 4.20240524.0

Commits

• See full diff in compare view

Updates wrangler from 3.48.0 to 3.57.1

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

• #5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

• #5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

  If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

• #5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

  Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

• #5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

[email protected]

Minor Changes

• #5696 7e97ba8 Thanks @​geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

• #5819 63f7acb Thanks @​CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure

  Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:

  ✨ Deployment complete!
  

  This commit ensures that we provide users with:

  • the correct feedback with respect to their Pages deployment
  • the appropriate messaging depending on the status of their project's deployment status
  • the appropriate logs in case of a deployment failure

• #5814 2869e03 Thanks @​CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help

  Running wrangler pages --help will list, amongst others, the following global flags:

  -j, --experimental-json-config
  -c, --config
  -e, --env
  -h, --help
  -v, --version
  

  This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.

  This commit ensures we display the correct global flags that apply to Pages.

• #5818 df2daf2 Thanks @​WalshyDev! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.57.1

Patch Changes

• #5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

• #5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

  If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

• #5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

  Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

• #5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

3.57.0

Minor Changes

• #5696 7e97ba8 Thanks @​geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

• #5819 63f7acb Thanks @​CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure

  Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:

  ✨ Deployment complete!
  

  This commit ensures that we provide users with:

  • the correct feedback with respect to their Pages deployment
  • the appropriate messaging depending on the status of their project's deployment status
  • the appropriate logs in case of a deployment failure

• #5814 2869e03 Thanks @​CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help

  Running wrangler pages --help will list, amongst others, the following global flags:

  -j, --experimental-json-config
  -c, --config
  -e, --env
  -h, --help
  -v, --version
  

... (truncated)

Commits

• 29483dc Version Packages (#5870)
• f2ceb3a queue consumer setting max_batch_timeout, batch-timeout should accept 0 (#5859)
• d5e00e4 Remove Hyperdrive warning log indicating that Hyperdrive local binding does n...
• a12b031 ignore workerd CODE_MOVED error (#5626)
• 441a05f fix(wrangler): wrangler pages deploy should fail if deployment failed (#5862)
• 65902d5 Version Packages (#5837)
• df2daf2 Deprecate "deployment" in metadata binding (#5818)
• 7e97ba8 D1: execute --file --remote now uses dedicated import API (#5696)
• 95a1fa1 fix(wrangler): Make jest inline snapshots work with prettier 3 (#5851)
• 36cb22b fix(wrangler): Display correct global flags in wrangler pages --help (#5849)
• Additional commits viewable in compare view

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Superseded by #420.