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.

Sign up for GitHub

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

Jump to bottom

chore(tests-e2e): update dependency wrangler to v3.90.0 #275

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(tests-e2e): update dependency wrangler to v3.90.0 #275

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 23, 2024

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v3.90.0

Compare Source

Minor Changes
Patch Changes

v3.89.0

Compare Source

Minor Changes
Patch Changes

  • #​7314 a30c805 Thanks @​Ankcorn! - Fix observability.logs.enabled validation

  • #​7285 fa21312 Thanks @​penalosa! - Rename directory to projectRoot and ensure it's relative to the wrangler.toml. This fixes a regression which meant that .wrangler temporary folders were inadvertently generated relative to process.cwd() rather than the location of the wrangler.toml file. It also renames directory to projectRoot, which affects the `unstable_startWorker() interface.

  • Updated dependencies [563439b]:

v3.88.0

Compare Source

Minor Changes

  • #​7173 b6cbfbd Thanks @​Ankcorn! - Adds [observability.logs] settings to wrangler. This setting lets developers control the settings for logs as an independent dataset enabling more dataset types in the future. The most specific setting will win if any of the datasets are not enabled.

    It also adds the following setting to the logs config

    • invocation_logs - set to false to disable invocation logs. Defaults to true.
    [observability.logs]
enabled = true
invocation_logs = false

  • #​7207 edec415 Thanks @​jonesphillip! - Added r2 bucket lifecycle command to Wrangler including list, add, remove, set

Patch Changes

v3.87.0

Compare Source

Minor Changes
Patch Changes

v3.86.1

Compare Source

Patch Changes

v3.86.0

Compare Source

Minor Changes
Patch Changes

v3.85.0

Compare Source

Minor Changes

  • #​7105 a5f1779 Thanks @​jonesphillip! - Added the ability to list, add, remove, and update R2 bucket custom domains.

  • #​7132 89f6274 Thanks @​gabivlj! - Event messages are capitalized, images of wrong architectures properly show the error in cloudchamber create
    When a new "health" enum is introduced, wrangler cloudchamber list won't crash anymore.
    Update Cloudchamber schemas.

  • #​7121 2278616 Thanks @​bruxodasilva! - Added pause and resume commands to manage Workflows and hidded unimplemented delete command

Patch Changes

v3.84.1

Compare Source

Patch Changes

v3.84.0

Compare Source

Minor Changes
Patch Changes

  • #​7091 68a2a84 Thanks @​taylorlee! - fix: synchronize observability settings during wrangler versions deploy

    When running wrangler versions deploy, Wrangler will now update observability settings in addition to logpush and tail_consumers. Unlike wrangler deploy, it will not disable observability when observability is undefined in wrangler.toml.

  • #​7080 924ec18 Thanks @​vicb! - chore(wrangler): update unenv dependency version

  • #​7097 8ca4b32 Thanks @​emily-shen! - fix: remove deprecation warnings for wrangler init

    We will not be removing wrangler init (it just delegates to create-cloudflare now). These warnings were causing confusion for users as it wrangler init is still recommended in many places.

  • #​7073 656a444 Thanks @​penalosa! - Internal refactor to remove es-module-lexer and support wrangler types for Workers with Durable Objects & JSX

  • #​7024 bd66d51 Thanks @​xortive! - fix: make individual parameters work for wrangler hyperdrive create when not using HoA

    wrangler hyperdrive create individual parameters were not setting the database name correctly when calling the api.

  • #​7024 bd66d51 Thanks @​xortive! - refactor: use same param parsing code for wrangler hyperdrive create and wrangler hyperdrive update

    ensures that going forward, both commands support the same features and have the same names for config flags

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

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 renovate bot requested a review from satanTime as a code owner November 23, 2024 02:44
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Nov 23, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: tests-e2e/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: @cloudflare/[email protected]
npm error node_modules/@cloudflare/workers-types
npm error   dev @cloudflare/workers-types@"4.20240821.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @cloudflare/workers-types@"^4.20241106.0" from [email protected]
npm error node_modules/wrangler
npm error   dev wrangler@"3.90.0" from the root project
npm error
npm error Conflicting peer dependency: @cloudflare/[email protected]
npm error node_modules/@cloudflare/workers-types
npm error   peerOptional @cloudflare/workers-types@"^4.20241106.0" from [email protected]
npm error   node_modules/wrangler
npm error     dev wrangler@"3.90.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-23T02_44_07_786Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-23T02_44_07_786Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@satanTime satanTime Awaiting requested review from satanTime satanTime is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants