#417188f15f61 Thanks @penalosa! - patch: This release fixes some regressions related to running wrangler dev that were caused by internal refactoring of the dev server architecture (#3960). The change has been reverted, and will be added back in a future release.
#3960c36b78b4 Thanks @RamIdeas! - Refactoring the internals of wrangler dev servers (including wrangler dev, wrangler dev --remote and unstable_dev()).
There are no changes required for developers to opt-in. Improvements include:
fewer 'address in use' errors upon reloads
upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker
Patch Changes
#3590f4ad634a Thanks @penalosa! - fix: When a middleware is configured which doesn't support your Worker's script format, fail early with a helpful error message
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.
So that it's less confusing when tailing a worker that consumes events from a Queue.
Patch Changes
#26873077016f 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.
#4069f4d28918 Thanks @a-robinson! - Default new Hyperdrive configs for PostgreSQL databases to port 5432 if the port is not specified
#417188f15f61 Thanks @penalosa! - patch: This release fixes some regressions related to running wrangler dev that were caused by internal refactoring of the dev server architecture (#3960). The change has been reverted, and will be added back in a future release.
#3960c36b78b4 Thanks @RamIdeas! - Refactoring the internals of wrangler dev servers (including wrangler dev, wrangler dev --remote and unstable_dev()).
There are no changes required for developers to opt-in. Improvements include:
fewer 'address in use' errors upon reloads
upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker
Patch Changes
#3590f4ad634a Thanks @penalosa! - fix: When a middleware is configured which doesn't support your Worker's script format, fail early with a helpful error message
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.
So that it's less confusing when tailing a worker that consumes events from a Queue.
Patch Changes
#26873077016f 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.
#4069f4d28918 Thanks @a-robinson! - Default new Hyperdrive configs for PostgreSQL databases to port 5432 if the port is not specified
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)
Bumps wrangler from 3.5.1 to 3.13.1.
Release notes
Sourced from wrangler's releases.
... (truncated)
Changelog
Sourced from wrangler's changelog.
... (truncated)
Commits
a08c292
Version Packages (#4163)88f15f6
Revert "startDevWorker - Milestone 1" (#4171)2a0eefd
Version Packages (#4160)403bc25
Fix wrangler generated types to match runtime exports (#4161)c36b78b
startDevWorker - Milestone 1 (#3960)f4ad634
Bail early on middleware format mismatch (#3590)763ecce
Version Packages (#4126)bfc9a3e
Bump miniflare to3.20231010.0
(#4155)c33a636
wrangler: add mutable id to first_party_worker logs (#4132)93833f0
Support Queue events in tail (#2397)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