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.58.0 in the cloudflare group across 1 directory #367

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

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

Updates wrangler from 3.53.1 to 3.58.0

Release notes

Sourced from wrangler's releases.

wrangler@3.58.0

Minor Changes

  • #5933 93b98cb Thanks @​WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.

Patch Changes

  • #5938 9e4d8bc Thanks @​threepointone! - fix: let "assets" in wrangler.toml be a string

    The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode's even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.

  • #5758 8e5e589 Thanks @​Jackenmen! - fix: use correct type for AI binding instead of unknown

  • Updated dependencies [e0e7725]:

    • miniflare@3.20240524.1

wrangler@3.57.2

Patch Changes

  • #5905 53f22a0 Thanks @​penalosa! - fix: Remove WARP certificate injection. Instead, you should ensure that any custom certificates that are needed are included in NODE_EXTRA_CA_CERTS.

  • #5930 57daae0 Thanks @​WalshyDev! - chore: improve error message when updating secret for a non-deployed latest version.

  • #5703 a905f31 Thanks @​penalosa! - fix: Don't use ExportedHandler["middleware"] for injecting middleware

  • Updated dependencies [64ccdd6, 4458a9e]:

    • miniflare@3.20240524.0

wrangler@3.57.1

Patch Changes

  • #5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

  • #5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

    If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

  • #5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

    Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

  • #5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

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.

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.58.0

Minor Changes

  • #5933 93b98cb Thanks @​WalshyDev! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.

Patch Changes

  • #5938 9e4d8bc Thanks @​threepointone! - fix: let "assets" in wrangler.toml be a string

    The experimental "assets" field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode's even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.

  • #5758 8e5e589 Thanks @​Jackenmen! - fix: use correct type for AI binding instead of unknown

  • Updated dependencies [e0e7725]:

    • miniflare@3.20240524.1

3.57.2

Patch Changes

  • #5905 53f22a0 Thanks @​penalosa! - fix: Remove WARP certificate injection. Instead, you should ensure that any custom certificates that are needed are included in NODE_EXTRA_CA_CERTS.

  • #5930 57daae0 Thanks @​WalshyDev! - chore: improve error message when updating secret for a non-deployed latest version.

  • #5703 a905f31 Thanks @​penalosa! - fix: Don't use ExportedHandler["middleware"] for injecting middleware

  • Updated dependencies [64ccdd6, 4458a9e]:

    • miniflare@3.20240524.0

3.57.1

Patch Changes

  • #5859 f2ceb3a Thanks @​w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value

  • #5862 441a05f Thanks @​CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

    If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

  • #5812 d5e00e4 Thanks @​thomasgauvin! - fix: remove Hyperdrive warning for local development.

    Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

  • #5626 a12b031 Thanks @​RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

3.57.0

... (truncated)

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 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 5 months ago

⚠️ No Changeset found

Latest commit: e79c95e00173ef2fb85c0f6b3006709855c2c771

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 5 months ago

Superseded by #371.