search

andykenward / github-actions-cloudflare-pages

GitHub Action to deploy to Cloudflare Pages
MIT License
16 stars 0 forks source link

chore(deps): bump wrangler from 3.53.1 to 3.57.0 in the cloudflare group across 1 directory #358

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the cloudflare group with 1 update in the / directory: wrangler.

Updates wrangler from 3.53.1 to 3.57.0

Release notes

Sourced from wrangler's releases.

wrangler@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

    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.

    If you're currently using the old binding, please move over to the new version_metadata binding by adding:

    [version_metadata]
binding = "CF_VERSION_METADATA"

    and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

Patch Changes

  • #5838 609debd Thanks @​petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability

  • #5832 86a6e09 Thanks @​petebacondarwin! - fix: do not allow non-string values in bulk secret uploads

    Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a JSON file that contained non-string secrets, since these are not supported

... (truncated)

Changelog

Sourced from wrangler's changelog.

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

    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.

    If you're currently using the old binding, please move over to the new version_metadata binding by adding:

    [version_metadata]
binding = "CF_VERSION_METADATA"

    and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

Patch Changes

... (truncated)

Commits
  • 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)
  • 2869e03 fix(wrangler): Display correct global flags in wrangler pages --help (#5814)
  • 82415b5 Implement additional E2E tests for wrangler dev (--remote) (#4486)
  • baaebf6 chore: enforce curly braces for if, while, etc blocks (#5842)
  • 63f7acb fix(wrangler): Show feedback on Pages Function upload failure (#5819)
  • 9c469f6 Update pnpm etc (#5809)
  • 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
changeset-bot[bot] commented 4 months ago

⚠️ No Changeset found

Latest commit: f0456409ea6885fb9764278afe2ca09ce9720135

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

dependabot[bot] commented 4 months ago

Superseded by #362.