Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps-dev): bump wrangler from 3.95.0 to 3.96.0 #1898

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 16, 2024

Bumps wrangler from 3.95.0 to 3.96.0.

Release notes

Sourced from wrangler's releases.

wrangler@3.96.0

Minor Changes

Patch Changes

  • #7542 f13c897 Thanks @​CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commands

    Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.

  • #6754 0356d0a Thanks @​bluwy! - refactor: move @cloudflare/workers-shared as dev dependency

  • #7478 2e90efc Thanks @​petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environment

    It is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration. But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment. Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration. Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.

  • #7524 11f95f7 Thanks @​gpanders! - Include response body in Cloudchamber API errors

  • #7427 3bc0f28 Thanks @​edmundhung! - The x-provision experimental flag now identifies draft and inherit bindings by looking up the current binding settings.

    Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during wrangler deploy.

  • Updated dependencies []:

    • miniflare@3.20241205.0
Changelog

Sourced from wrangler's changelog.

3.96.0

Minor Changes

Patch Changes

  • #7542 f13c897 Thanks @​CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commands

    Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.

  • #6754 0356d0a Thanks @​bluwy! - refactor: move @cloudflare/workers-shared as dev dependency

  • #7478 2e90efc Thanks @​petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environment

    It is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration. But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment. Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration. Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.

  • #7524 11f95f7 Thanks @​gpanders! - Include response body in Cloudchamber API errors

  • #7427 3bc0f28 Thanks @​edmundhung! - The x-provision experimental flag now identifies draft and inherit bindings by looking up the current binding settings.

    Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during wrangler deploy.

  • Updated dependencies []:

    • miniflare@3.20241205.0
Commits
  • d4626f1 Version Packages (#7514)
  • 6cac351 Revert "Don't require Hyperdrive local connection string when using wrangler ...
  • eba018e cloudchamber/create: always print deployment and placement ID (#7523)
  • 004af53 PIPE-155 Add pipelines prefix option (#7510)
  • 3bc0f28 feat(wrangler): identify draft and inherit bindings and provision draft ones ...
  • a98dfa0 Don't require Hyperdrive local connection string when using wrangler dev --re...
  • 34d0d46 test: try harder to delete Workers Sites KV store in e2e tests (#7515)
  • 11f95f7 cloudchamber/curl: include response body in API errors (#7524)
  • 2e90efc fix: ensure that non-inherited fields are not removed when using an inferred ...
  • 8af3365 Add r2 bucket domain get command (#7383)
  • 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 <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)

Bumps [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) from 3.95.0 to 3.96.0.
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@3.96.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Dec 16, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 17, 2024

Looks like wrangler is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Dec 17, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/wrangler-3.96.0 branch December 17, 2024 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants