LeetCode-Stats-Card icon indicating copy to clipboard operation
LeetCode-Stats-Card copied to clipboard

Published 20 hours ago • verified publisher icon JacobLinCool

chore(deps): update dependency wrangler to v3.83.0

Open renovate[bot] opened this issue 1 year ago • 1 comments
trafficstars

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
wrangler (source) 3.30.1 -> 3.83.0 age adoption passing confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v3.83.0

Compare Source

Minor Changes
  • #​7000 1de309b Thanks @​jkoe-cf! - feature: allowing users to specify a description when creating an event notification rule
Patch Changes

v3.82.0

Compare Source

Minor Changes
Patch Changes

  • #​5737 9bf51d6 Thanks @​penalosa! - Validate duplicate bindings across all binding types

  • #​7010 1f6ff8b Thanks @​vicb! - chore: update unenv dependency version

  • #​7012 244aa57 Thanks @​RamIdeas! - Add support for Workflow bindings (in deployments, not yet in local dev)

    To bind to a workflow, add a workflows section in your wrangler.toml:

    [[workflows]]
binding = "WORKFLOW"
name = "my-workflow"
class_name = "MyDemoWorkflow"

    and export an entrypoint (e.g. MyDemoWorkflow) in your script:

    import { WorkflowEntrypoint } from "cloudflare:workers";

export class MyDemoWorkflow extends WorkflowEntrypoint<Env, Params> {...}

  • #​7039 e44f496 Thanks @​penalosa! - Only show dev registry connection status in local dev

  • #​7037 e1b93dc Thanks @​emily-shen! - fix: ask for confirmation before creating a new Worker when uploading secrets

    Previously, wrangler secret put KEY --name non-existent-worker would automatically create a new Worker with the name non-existent-worker. This fix asks for confirmation before doing so (if running in an interactive context). Behaviour in non-interactive/CI contexts should be unchanged.

  • #​7015 48152d6 Thanks @​RamIdeas! - add wrangler workflows ... commands

  • #​7041 045787b Thanks @​CarmenPopoviciu! - Show wrangler pages dev --proxy warning

    On Node.js 17+, wrangler will default to fetching only the IPv6 address. With these changes we warn users that the process listening on the port specified via --proxy should be configured for IPv6.

  • #​7018 127615a Thanks @​emily-shen! - fix: log successful runs of d1 execute in local

  • #​6970 a8ca700 Thanks @​oliy! - Add HTTP authentication options for Workers Pipelines

  • #​7005 6131ef5 Thanks @​edmundhung! - fix: prevent users from passing multiple arguments to non array options

  • #​7046 f9d5fdb Thanks @​oliy! - Minor change to 3rd party API shape for Workers Pipelines

  • #​6972 c794935 Thanks @​penalosa! - Add (local) indicator to bindings using local data

  • Updated dependencies [809193e]:

v3.81.0

Compare Source

Minor Changes
Patch Changes

  • #​6963 a5ac45d Thanks @​RamIdeas! - fix: make wrangler dev --remote respect wrangler.toml's account_id property.

    This was a regression in the --x-dev-env flow recently turned on by default.

  • #​6996 b8ab809 Thanks @​emily-shen! - fix: improve error messaging when accidentally using Workers commands in Pages project

    If we detect a Workers command used with a Pages project (i.e. wrangler.toml contains pages_output_build_dir), error with Pages version of command rather than "missing entry-point" etc.

v3.80.5

Compare Source

Patch Changes

v3.80.4

Compare Source

Patch Changes

v3.80.3

Compare Source

Patch Changes

v3.80.2

Compare Source

Patch Changes
  • #​6923 1320f20 Thanks @​andyjessop! - chore: adds eslint-disable for ESLint error on empty typescript interface in workers-configuration.d.ts

v3.80.1

Compare Source

Patch Changes

v3.80.0

Compare Source

Minor Changes

  • #​6408 3fa846e Thanks @​RamIdeas! - feat: update the --experimental-dev-env (shorthand: --x-dev-env) flag to on-by-default

    If you experience any issues, you can disable the flag with --x-dev-env=false. Please also let us know by opening an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose.

Patch Changes

  • #​6854 04a8fed Thanks @​penalosa! - chore: Include serialised FormData in debug logs

  • #​6879 b27d8cb Thanks @​petebacondarwin! - fix: the docs command should not crash if given search terms

    Fixes a regression accidentally introduced by #​3735.

  • #​6873 b123f43 Thanks @​zwily! - fix: reduce logging noise during wrangler dev with static assets

    Updates to static assets are accessible by passing in --log-level="debug" but otherwise hidden.

  • #​6881 7ca37bc Thanks @​RamIdeas! - fix: custom builds outputting files in assets watched directory no longer cause the custom build to run again in an infinite loop

  • #​6872 b2d094e Thanks @​petebacondarwin! - fix: render a helpful build error if a Service Worker mode Worker has imports

    A common mistake is to forget to export from the entry-point of a Worker, which causes Wrangler to infer that we are in "Service Worker" mode.

    In this mode, imports to external modules are not allowed. Currently this only fails at runtime, because our esbuild step converts these imports to an internal __require() call that throws an error. The error message is misleading and does not help the user identify the cause of the problem. This is particularly tricky where the external imports are added by a library or our own node.js polyfills.

    Fixes #​6648

  • #​6792 27e8385 Thanks @​penalosa! - fix: Handle more module declaration cases

  • #​6838 7dbd0c8 Thanks @​GregBrimble! - fix: Improve static asset upload messaging

v3.79.0

Compare Source

Minor Changes
  • #​6801 6009bb4 Thanks @​RamIdeas! - feat: implement retries within wrangler deploy and wrangler versions upload to workaround spotty network connections and service flakes
Patch Changes

v3.78.12

Compare Source

Patch Changes

v3.78.11

Compare Source

Patch Changes

v3.78.10

Compare Source

Patch Changes

v3.78.9

Compare Source

Patch Changes

v3.78.8

Compare Source

Patch Changes

  • #​6791 74d719f Thanks @​penalosa! - fix: Add missing binding to init --from-dash

  • #​6728 1ca313f Thanks @​emily-shen! - fix: remove filepath encoding on asset upload and handle sometimes-encoded characters

    Some characters like [ ] @​ are encoded by encodeURIComponent() but are often requested at an unencoded URL path. This change will make assets with filenames with these characters accessible at both the encoded and unencoded paths, but to use the encoded path as the canonical one, and to redirect requests to the canonical path if necessary.

  • #​6798 7d7f19a Thanks @​emily-shen! - fix: error if an asset binding is provided without a Worker script

  • Updated dependencies [1ca313f]:

v3.78.7

Compare Source

Patch Changes

  • #​6775 ecd82e8 Thanks @​CarmenPopoviciu! - fix: Support switching between static and dynamic Workers

    This commit fixes the current behaviour of watch mode for Workers with assets, and adds support for switching between static and dynamic Workers within a single wrangler dev session.

  • #​6762 2840b9f Thanks @​petebacondarwin! - fix: error if a user inadvertently uploads a Pages _workers.js file or directory as an asset

  • #​6778 61dd93a Thanks @​CarmenPopoviciu! - fix: Error if Workers + Assets are run in remote mode

    Workers + Assets are currently supported only in local mode. We should throw an error if users attempt to use Workers with assets in remote mode.

  • #​6782 7655505 Thanks @​vicb! - chore: update unenv dependency version

  • #​6777 9649dbc Thanks @​penalosa! - chore: Update CI messaging

  • #​6779 3e75612 Thanks @​emily-shen! - fix: include asset binding in wrangler types

v3.78.6

Compare Source

Patch Changes

  • #​6743 b45e326 Thanks @​petebacondarwin! - fix: ability to build tricky Node.js compat scenario Workers

    Adds support for non-default build conditions and platform via the WRANGLER_BUILD_CONDITIONS and WRANGLER_BUILD_PLATFORM flags.

    Fixes https://github.com/cloudflare/workers-sdk/issues/6742

  • #​6776 02de103 Thanks @​zebp! - fix: disable observability on deploy if not explicitly defined in config

    When deploying a Worker that has observability enabled in the deployed version but not specified in the wrangler.toml Wrangler will now set observability to disabled for the new version to match the wrangler.toml as the source of truth.

  • Updated dependencies [2ddbb65]:

v3.78.5

Compare Source

Patch Changes

  • #​6744 e3136f9 Thanks @​petebacondarwin! - chore: update unenv dependency version

  • #​6749 9a06f88 Thanks @​CarmenPopoviciu! - fix: Throw error when attempting to configure Workers with assets and tail consumers

    Tail Workers are currently not supported for Workers with assets. This commit ensures we throw a corresponding error if users are attempting to configure tail_consumers via their configuration file, for a Worker with assets. This validation is applied for all wrangler dev, wrangler deploy, wrangler versions upload.

  • #​6746 0deb42b Thanks @​GregBrimble! - fix: Fix assets upload message to correctly report number of uploaded assets

  • #​6745 6dbbb88 Thanks @​jonesphillip! - fix: r2 bucket notification get <bucket_name> has been marked deprecated in favor of r2 bucket notification list <bucket_name> to reflect behavior.

  • Updated dependencies [2407c41]:

v3.78.4

Patch Changes

v3.78.3

Patch Changes

v3.78.2

Compare Source

Patch Changes

v3.78.1

Compare Source

Patch Changes

v3.78.0

Compare Source

Minor Changes
Patch Changes

v3.77.0

Compare Source

Minor Changes

  • #​6674 831f892 Thanks @​andyjessop! - feat: Added new [[pipelines]] bindings. This creates a new binding that allows sending events to the specified pipeline.

    Example:

    [[pipelines]] binding = "MY_PIPELINE" pipeline = "my-pipeline"

  • #​6668 88c40be Thanks @​zebp! - feature: add observability setting to wrangler.toml

    Adds the observability setting which provides your Worker with automatic persistent logs that can be searched, filtered, and queried directly from the Workers dashboard.

  • #​6679 2174127 Thanks @​jkoe-cf! - feat: adding option to specify a rule within the config to delete (if no rules are specified, all rules get deleted)

  • #​6666 4107f57 Thanks @​threepointone! - feat: support analytics engine in local/remote dev

    This adds "support" for analytics engine datasets for wrangler dev. Specifically, it simply mocks the AE bindings so that they exist while developing (and don't throw when accessed).

    This does NOT add support in Pages, though we very well could do so in a similar way in a followup.

  • #​6640 8527675 Thanks @​petebacondarwin! - feat: experimental workers assets can be ignored by adding a .assetsignore file

    This file can be added to the root of the assets directory that is to be uploaded alongside the Worker when using experimental_assets.

    The file follows the .gitignore syntax, and any matching paths will not be included in the upload.

  • #​6652 648cfdd Thanks @​bthwaites! - feat: Update R2 Get Event Notification response, display, and actions

  • #​6625 8dcd456 Thanks @​maxwellpeterson! - feature: Add support for placement hints

    Adds the hint field to smart placement configuration. When set, placement hints will be used to decide where smart-placement-enabled Workers are run.

  • #​6631 59a0072 Thanks @​emily-shen! - feat: Add config options 'html_handling' and 'not_found_handling' to experimental_asset field in wrangler.toml

Patch Changes

v3.76.0

Compare Source

Minor Changes

  • #​6126 18c105b Thanks @​IRCody! - feature: Add 'cloudchamber curl' command

    Adds a cloudchamber curl command which allows easy access to arbitrary cloudchamber API endpoints.

  • #​6649 46a91e7 Thanks @​andyjessop! - feature: Integrate the Cloudflare Pipelines product into wrangler.

    Cloudflare Pipelines is a product that handles the ingest of event streams into R2. This feature integrates various forms of managing pipelines.

    Usage: wrangler pipelines create <pipeline>: Create a new pipeline wrangler pipelines list: List current pipelines wrangler pipelines show <pipeline>: Show a pipeline configuration wrangler pipelines update <pipeline>: Update a pipeline wrangler pipelines delete <pipeline>: Delete a pipeline

    Examples: wrangler pipelines create my-pipeline --r2 MY_BUCKET --access-key-id "my-key" --secret-access-key "my-secret" wrangler pipelines show my-pipeline wrangler pipelines delete my-pipline

Patch Changes

v3.75.0

Compare Source

Minor Changes

  • #​6603 a197460 Thanks @​taylorlee! - feature: log version preview url when previews exist

    The version upload API returns a field indicating whether a preview exists for that version. If a preview exists and workers.dev is enabled, wrangler will now log the full URL on version upload.

    This does not impact wrangler deploy, which only prints the workers.dev route of the latest deployment.

  • #​6550 8d1d464 Thanks @​Pedr0Rocha! - feature: add RateLimit type generation to the ratelimit unsafe binding.

Patch Changes

  • #​6615 21a09e0 Thanks @​RamIdeas! - chore: avoid potential double-install of create-cloudflare

    When wrangler init delegates to C3, it did so via npm create [email protected]. C3's v2.5.0 was the first to include auto-update support to avoid npx's potentially stale cache. But this also guaranteed a double install for users who do not have 2.5.0 cached. Now, wrangler delegates via npm create cloudflare@^2.5.0 which should use the latest version cached on the user's system or install and use the latest v2.x.x.

  • #​6603 a197460 Thanks @​taylorlee! - chore: fix version upload log order

    Previously deploy prints: upload timings deploy timings current version id

    while version upload prints: worker version id upload timings

    This change makes version upload more similar to deploy by printing version id after upload, which also makes more sense, as version ID can only be known after upload has finished.

v3.74.0

Compare Source

Minor Changes
Patch Changes

v3.73.0

Compare Source

Minor Changes

  • #​6571 a7e1bfe Thanks @​penalosa! - feat: Add deployment http targets to wrangler deploy logs, and add url to pages deploy logs

  • #​6497 3bd833c Thanks @​WalshyDev! - chore: move wrangler versions ..., wrangler deployments ..., wrangler rollback and wrangler triggers ... out of experimental and open beta. These are now available to use without the --x-versions flag, you can continue to pass this however without issue to keep compatibility with all the usage today.

    A few of the commands had an output that wasn't guarded by --x-versions those have been updated to use the newer output, we have tried to keep compatibility where possible (for example: wrangler rollback will continue to output "Worker Version ID:" so users can continue to grab the ID). If you wish to use the old versions of the commands you can pass the --no-x-versions flag. Note, these will be removed in the future so please work on migrating.

  • #​6586 72ea742 Thanks @​penalosa! - feat: Inject a 404 response for browser requested favicon.ico files when loading the /__scheduled page for scheduled-only Workers

  • #​6497 3bd833c Thanks @​WalshyDev! - feat: update wrangler deploy to use the new versions and deployments API. This should have zero user-facing impact but sets up the most used command to deploy Workers to use the new recommended APIs and move away from the old ones. We will still call the old upload path where required (e.g. Durable Object migration or Service Worker format).

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • [ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] avatar Mar 05 '24 18:03 renovate[bot]