search

TampaDevs / api.jobs.tampa.dev

Tampa Devs Job Board API
5 stars 0 forks source link

Bump wrangler from 3.1.1 to 3.2.0 #57

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps wrangler from 3.1.1 to 3.2.0.

Release notes

Sourced from wrangler's releases.

wrangler@3.2.0

Minor Changes

  • #3583 78ddb8de Thanks @​penalosa! - Upgrade Miniflare (and hence workerd) to v3.20230710.0.

  • #3426 5a74cb55 Thanks @​matthewdavidrodgers! - Prefer non-force deletes unless a Worker is a dependency of another.

    If a Worker is used as a service binding, a durable object namespace, an outbounds for a dynamic dispatch namespace, or a tail consumer, then deleting that Worker will break those existing ones that depend upon it. Deleting with ?force=true allows you to delete anyway, which is currently the default in Wrangler.

    Force deletes are not often necessary, however, and using it as the default has unfortunate consequences in the API. To avoid them, we check if any of those conditions exist, and present the information to the user. If they explicitly acknowledge they're ok with breaking their other Workers, fine, we let them do it. Otherwise, we'll always use the much safer non-force deletes. We also add a "--force" flag to the delete command to skip the checks and confirmation and proceed with ?force=true

Patch Changes

  • #3585 e33bb44a Thanks @​mrbbot! - fix: register middleware once for module workers

    Ensure middleware is only registered on the first request when using module workers. This should prevent stack overflows and slowdowns when making large number of requests to wrangler dev with infrequent reloads.

  • #3547 e16d0272 Thanks @​jspspike! - Fixed issue with wrangler dev not finding imported files. Previously when wrangler dev would automatically reload on any file changes, it would fail to find any imported files.

wrangler@3.1.2

Patch Changes

Changelog

Sourced from wrangler's changelog.

3.2.0

Minor Changes

  • #3426 5a74cb55 Thanks @​matthewdavidrodgers! - Prefer non-force deletes unless a Worker is a dependency of another.

    If a Worker is used as a service binding, a durable object namespace, an outbounds for a dynamic dispatch namespace, or a tail consumer, then deleting that Worker will break those existing ones that depend upon it. Deleting with ?force=true allows you to delete anyway, which is currently the default in Wrangler.

    Force deletes are not often necessary, however, and using it as the default has unfortunate consequences in the API. To avoid them, we check if any of those conditions exist, and present the information to the user. If they explicitly acknowledge they're ok with breaking their other Workers, fine, we let them do it. Otherwise, we'll always use the much safer non-force deletes. We also add a "--force" flag to the delete command to skip the checks and confirmation and proceed with ?force=true

Patch Changes

  • #3585 e33bb44a Thanks @​mrbbot! - fix: register middleware once for module workers

    Ensure middleware is only registered on the first request when using module workers. This should prevent stack overflows and slowdowns when making large number of requests to wrangler dev with infrequent reloads.

  • #3547 e16d0272 Thanks @​jspspike! - Fixed issue with wrangler dev not finding imported files. Previously when wrangler dev would automatically reload on any file changes, it would fail to find any imported files.

3.1.2

Patch Changes

  • #3497 c5f3bf45 Thanks @​evanderkoogh! - Refactor dev-only checkedFetch check from a method substitution to a JavaScript Proxy to be able to support Proxied global fetch function.
  • #3403 8d1521e9 Thanks @​Cherry! - fix: wrangler generate will now work cross-device. This is very common on Windows install that use C:/ for the OS and another drive for user files.
Commits


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 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[bot] commented 1 year ago

Superseded by #58.