chore(deps-dev): bump wrangler from 3.11.0 to 3.12.0

[dependabot]

Bumps wrangler from 3.11.0 to 3.12.0.

Release notes

Sourced from wrangler's releases.

wrangler@3.12.0

Minor Changes

• #4071 f880a009 Thanks @​matthewdavidrodgers! - Support TailEvent messages in Tail sessions

  When tailing a tail worker, messages previously had a null event property. Following cloudflare/workerd#1248, these events have a valid event, specifying which scripts produced events that caused your tail worker to run.

  As part of rolling this out, we're filtering out tail events in the internal tail infrastructure, so we control when these new messages are forward to tail sessions, and can merge this freely.

  One idiosyncracy to note, however, is that tail workers always report an "OK" status, even if they run out of memory or throw. That is being tracked and worked on separately.

• #2397 93833f04 Thanks @​a-robinson! - feature: Support Queue consumer events in tail

  So that it's less confusing when tailing a worker that consumes events from a Queue.

Patch Changes

• #2687 3077016f Thanks @​jrf0110! - Fixes large Pages projects failing to complete direct upload due to expiring JWTs

  For projects which are slow to upload - either because of client bandwidth or large numbers of files and sizes - It's possible for the JWT to expire multiple times. Since our network request concurrency is set to 3, it's possible that each time the JWT expires we get 3 failed attempts. This can quickly exhaust our upload attempt count and cause the entire process to bail.

  This change makes it such that jwt refreshes do not count as a failed upload attempt.

• #4069 f4d28918 Thanks @​a-robinson! - Default new Hyperdrive configs for PostgreSQL databases to port 5432 if the port is not specified

Changelog

Sourced from wrangler's changelog.

3.12.0

Minor Changes

• #4071 f880a009 Thanks @​matthewdavidrodgers! - Support TailEvent messages in Tail sessions

  When tailing a tail worker, messages previously had a null event property. Following cloudflare/workerd#1248, these events have a valid event, specifying which scripts produced events that caused your tail worker to run.

  As part of rolling this out, we're filtering out tail events in the internal tail infrastructure, so we control when these new messages are forward to tail sessions, and can merge this freely.

  One idiosyncracy to note, however, is that tail workers always report an "OK" status, even if they run out of memory or throw. That is being tracked and worked on separately.

• #2397 93833f04 Thanks @​a-robinson! - feature: Support Queue consumer events in tail

  So that it's less confusing when tailing a worker that consumes events from a Queue.

Patch Changes

• #2687 3077016f Thanks @​jrf0110! - Fixes large Pages projects failing to complete direct upload due to expiring JWTs

  For projects which are slow to upload - either because of client bandwidth or large numbers of files and sizes - It's possible for the JWT to expire multiple times. Since our network request concurrency is set to 3, it's possible that each time the JWT expires we get 3 failed attempts. This can quickly exhaust our upload attempt count and cause the entire process to bail.

  This change makes it such that jwt refreshes do not count as a failed upload attempt.

• #4069 f4d28918 Thanks @​a-robinson! - Default new Hyperdrive configs for PostgreSQL databases to port 5432 if the port is not specified

Commits

• 763ecce Version Packages (#4126)
• bfc9a3e Bump miniflare to 3.20231010.0 (#4155)
• c33a636 wrangler: add mutable id to first_party_worker logs (#4132)
• 93833f0 Support Queue events in tail (#2397)
• 3077016 fix: Pages direct upload failing with expired JWT error (#2687)
• f4d2891 hyperdrive: Default to port 5432 if not specified (#4069)
• f880a00 Support TailEvent messages in Tail sessions (#4071)
• 08e5440 use Fetcher constructor (#4073)
• See full diff 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 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)

[dependabot]

Superseded by #12.