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

chore(deps): update dependency wrangler to v3.33.0 #497

Merged
merged 1 commit into from
Mar 13, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2024

Mend Renovate

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v3.33.0

Compare Source

Minor Changes
  • #​4930 2680462 Thanks @​rozenmd! - refactor: default wrangler d1 execute and wrangler d1 migrations commands to local mode first, to match wrangler dev

    This PR defaults wrangler d1 execute and wrangler d1 migrations commands to use the local development environment provided by wrangler to match the default behaviour in wrangler dev.

    BREAKING CHANGE (for a beta feature): wrangler d1 execute and wrangler d1 migrations commands now default --local to true. When running wrangler d1 execute against a remote D1 database, you will need to provide the --remote flag.

Patch Changes
  • #​5184 046930e Thanks @​nora-soderlund! - fix: change d1 migrations create to use the highest migration number rather than the first non-existing migration number to allow for gaps in the migration files.

  • Updated dependencies [1235d48, 27fb22b]:

    • miniflare@3.20240304.1

v3.32.0

Compare Source

Minor Changes
Patch Changes
  • #​5089 5b85dc9 Thanks @​DaniFoldi! - fix: include all currently existing bindings in wrangler types

    Add support for Email Send, Vectorize, Hyperdrive, mTLS, Browser Rendering and Workers AI bindings in wrangler types

    For example, from the following wrangler.toml setup:

    [browser]
    binding = "BROWSER"
    
    [ai]
    binding = "AI"
    
    [[send_email]]
    name = "SEND_EMAIL"
    
    [[vectorize]]
    binding = "VECTORIZE"
    index_name = "VECTORIZE_NAME"
    
    [[hyperdrive]]
    binding = "HYPERDRIVE"
    id = "HYPERDRIVE_ID"
    
    [[mtls_certificates]]
    binding = "MTLS"
    certificate_id = "MTLS_CERTIFICATE_ID"

    Previously, nothing would have been included in the generated Environment.
    Now, the following will be generated:

    interface Env {
    	SEND_EMAIL: SendEmail;
    	VECTORIZE: VectorizeIndex;
    	HYPERDRIVE: Hyperdrive;
    	MTLS: Fetcher;
    	BROWSER: Fetcher;
    	AI: Fetcher;
    }
  • Updated dependencies [11951f3, 11951f3]:

    • miniflare@3.20240304.0

v3.31.0

Compare Source

Minor Changes
Patch Changes
  • #​5132 82a3f94 Thanks @​mrbbot! - fix: switch default logging level of unstable_dev() to warn

    When running unstable_dev() in its default "test mode", the logging level was set to none. This meant any Worker startup errors or helpful warnings wouldn't be shown. This change switches the default to warn. To restore the previous behaviour, include logLevel: "none" in your options object:

    const worker = await unstable_dev("path/to/script.js", {
    	logLevel: "none",
    });
  • #​5128 d27e2a7 Thanks @​taylorlee! - fix: Add legacy_env support to experimental versions upload command.

  • #​5087 a5231de Thanks @​dario-piotrowicz! - fix: make wrangler types always generate a d.ts file for module workers

    Currently if a config file doesn't define any binding nor module, running
    wrangler types against such file would not produce a d.ts file.

    Producing a d.ts file can however still be beneficial as it would define a correct
    env interface (even if empty) that can be expanded/referenced by user code (this can
    be particularly convenient for scaffolding tools that may want to always generate an
    env interface).

    Example:
    Before wrangler types --env-interface MyEnv run with an empty wrangler.toml file
    would not generate any file, after these change it would instead generate a file with
    the following content:

    interface MyEnv {
    }
    
  • #​5138 3dd9089 Thanks @​G4brym! - fix: ensure Workers-AI local mode fetcher returns headers to client worker

  • Updated dependencies [42bcc72, 42bcc72]:

    • miniflare@3.20240223.1

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 has been generated by Mend Renovate. View repository job log here.

Copy link

github-actions bot commented Mar 5, 2024

🚨 Rust Panic Audit: 87 Potential Panic Points Detected 🚨

Crate: federation_query_planner

📊 Total Usages: 51

  • 🚨 panic usages: 3
  • 🎁 unwrap usages: 30
  • 🔎 expect usages: 8
  • 🔢 array_index usages: 10

Crate: engine

📊 Total Usages: 11

  • 🔎 expect usages: 1
  • 🎁 unwrap usages: 7
  • 🚨 panic usages: 3

Crate: telemetry

📊 Total Usages: 9

  • 🔢 array_index usages: 5
  • 🎁 unwrap usages: 4

Crate: tracing

📊 Total Usages: 6

  • 🔎 expect usages: 1
  • 🎁 unwrap usages: 5

Crate: cloudflare_worker

📊 Total Usages: 6

  • 🎁 unwrap usages: 5
  • 🚨 panic usages: 1

Crate: conductor

📊 Total Usages: 3

  • 🚨 panic usages: 1
  • 🔎 expect usages: 1
  • 🎁 unwrap usages: 1

Crate: config

📊 Total Usages: 1

  • 🚨 panic usages: 1

📌 Expected Annotations

Crate: config

📊 Total Expected Usages: 9

expand details
  1. Reason: "👇"
  • Code: let raw_contents = read_to_string(file_path)
  • Location: ./libs/config/src/lib.rs:597
  1. Reason: "👇"
  • Code: panic!("Failed to interpolate config file, please resolve the above errors");
  • Location: ./libs/config/src/lib.rs:629
  1. Reason: "👇"
  • Code: parse_config_from_json(&config_string).expect("Failed to parse JSON config file")
  • Location: ./libs/config/src/lib.rs:636
  1. Reason: "👇"
  • Code: parse_config_from_yaml(&config_string).expect("Failed to parse YAML config file")
  • Location: ./libs/config/src/lib.rs:640
  1. Reason: "👇"
  • Code: _ => panic!("Unsupported config file extension"),
  • Location: ./libs/config/src/lib.rs:657
  1. Reason: "👇"
  • Code: None => panic!("Config file has no extension"),
  • Location: ./libs/config/src/lib.rs:660
  1. Reason: "statically defined regex pattern, we know it works ;)"
  • Code: .unwrap();
  • Location: ./libs/config/src/interpolate.rs:18
  1. Reason: "part of development docgen CLI"
  • Code: .expect("Failed to serialize json schema for config file!");
  • Location: ./libs/config/src/generate-json-schema.rs:50
  1. Reason: "part of development docgen CLI"
  • Code: .expect("Failed to write the json schema to the file system!");
  • Location: ./libs/config/src/generate-json-schema.rs:54

Crate: conductor

📊 Total Expected Usages: 2

expand details
  1. Reason: "we need to exit the process, if the logger can't be correctly set."
  • Code: tracing::subscriber::set_global_default(subscriber).expect("failed to set up tracing");
  • Location: ./bin/conductor/src/lib.rs:37
  1. Reason: "we need to exit the process, if the provided configuration file is incorrect."
  • Code: panic!("Failed to initialize gateway: {:?}", e);
  • Location: ./bin/conductor/src/lib.rs:76

Crate: vrl

📊 Total Expected Usages: 2

expand details
  1. Reason: "if the provided VRL code in the config file can't compile, we have to exit."
  • Code: panic!("failed to compile vrl program");
  • Location: ./plugins/vrl/src/plugin.rs:122
  1. Reason: "states is a non-user provided variable"
  • Code: .expect("can't merge states when states is an empty vector!")
  • Location: ./plugins/vrl/src/plugin.rs:139

Crate: engine

📊 Total Expected Usages: 5

expand details
  1. Reason: "without a fetcher, there's no executor, without an executor, there's no gateway."
  • Code: panic!(
  • Location: ./libs/engine/src/source/graphql_source.rs:30
  1. Reason: "without a fetcher, there's no executor, without an executor, there's no gateway."
  • Code: panic!("Failed while initializing the executor's fetcher for Federation source");
  • Location: ./libs/engine/src/source/federation_source.rs:111
  1. Reason: "without a fetcher, there's no executor, without an executor, there's no gateway."
  • Code: panic!("Failed while initializing the executor's fetcher for Federation source");
  • Location: ./libs/engine/src/source/federation_source.rs:142
  1. Reason: "if we are unable to construct the endpoints and attach them onto the gateway's http server, we have to exit"
  • Code: Err(e) => panic!("failed to construct endpoint: {:?}", e),
  • Location: ./libs/engine/src/gateway.rs:147
  1. Reason: "we can safely index here, it's inside a test with constant defined fixtures."
  • Code: ConductorGateway::execute(request, &gw.routes[0].route_data).await
  • Location: ./libs/engine/src/gateway.rs:179

Crate: cloudflare_worker

📊 Total Expected Usages: 4

expand details
  1. Reason: "it panics only if the header name is not valid, and we know it is."
  • Code: .unwrap()
  • Location: ./bin/cloudflare_worker/src/http_tracing.rs:20
  1. Reason: "it panics only if the URL source is not valid, and it's already validated before."
  • Code: let url = req.url().unwrap();
  • Location: ./bin/cloudflare_worker/src/http_tracing.rs:23
  1. Reason: "it only panics if we are not running in a CF context, should be safe."
  • Code: let cf_info = req.cf().unwrap();
  • Location: ./bin/cloudflare_worker/src/http_tracing.rs:27
  1. Reason: "unwraps only in special cases where "data:text" is used."
  • Code: let http_host = url.host().unwrap().to_string();
  • Location: ./bin/cloudflare_worker/src/http_tracing.rs:36

Crate: jwt_auth

📊 Total Expected Usages: 1

expand details
  1. Reason: "if initiating an http client fails, then we have to exit."
  • Code: let client = wasm_polyfills::create_http_client().build().unwrap();
  • Location: ./plugins/jwt_auth/src/jwks_provider.rs:49

Crate: common

📊 Total Expected Usages: 1

expand details
  1. Reason: "we're parsing a statically defined constant, we know it works ;)"
  • Code: .unwrap()
  • Location: ./libs/common/src/graphql.rs:23

Crate: napi

📊 Total Expected Usages: 1

expand details
  1. Reason: "we need this"
  • Code: panic!("Exited process!")
  • Location: ./libs/napi/src/lib.rs:18

Copy link

github-actions bot commented Mar 5, 2024

🐋 This PR was built and pushed to the following Docker images:

Docker Bake metadata
{
"conductor": {
  "buildx.build.ref": "builder-ebcf6f9d-5f90-4544-8744-31239650da81/builder-ebcf6f9d-5f90-4544-8744-31239650da810/6uxy6xkv850pgmvwqhiny63ou",
  "containerimage.config.digest": "sha256:54154c91c42d557b1a55cea46016f4bafbb23241f0604a0e723379ef7428d953",
  "containerimage.descriptor": {
    "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
    "digest": "sha256:69488ef1299fe39bbdedfc0b08aa23a36b8b4e1f0c2de964b1d146e397f8708d",
    "size": 902,
    "platform": {
      "architecture": "amd64",
      "os": "linux"
    }
  },
  "containerimage.digest": "sha256:69488ef1299fe39bbdedfc0b08aa23a36b8b4e1f0c2de964b1d146e397f8708d",
  "image.name": "ghcr.io/the-guild-org/conductor/conductor:b8b2e2db4d2212a8a8df2365c8fe0e6428d0b373"
}
}

Copy link

github-actions bot commented Mar 5, 2024

✅ Benchmark Results

     data_received..................: 13 MB   221 kB/s
     data_sent......................: 22 MB   363 kB/s
     http_req_blocked...............: min=1.04µs   avg=2.97µs   med=2.22µs   max=1.32ms  p(95)=3.26µs   p(99)=11.36µs 
     http_req_connecting............: min=0s       avg=393ns    med=0s       max=1.28ms  p(95)=0s       p(99)=0s      
     http_req_duration..............: min=316.65µs avg=411.94µs med=385.1µs  max=25.24ms p(95)=482.64µs p(99)=588.15µs
       { expected_response:true }...: min=316.65µs avg=411.94µs med=385.1µs  max=25.24ms p(95)=482.64µs p(99)=588.15µs
     ✓ { scenario:rps_1000 }........: min=316.65µs avg=411.94µs med=385.1µs  max=25.24ms p(95)=482.64µs p(99)=588.15µs
     http_req_failed................: 0.00%   ✓ 0          ✗ 60001
     ✓ { scenario:rps_1000 }........: 0.00%   ✓ 0          ✗ 60001
     http_req_receiving.............: min=10.05µs  avg=26.2µs   med=25.63µs  max=1.15ms  p(95)=33.93µs  p(99)=40.97µs 
     http_req_sending...............: min=6.77µs   avg=15.55µs  med=14.41µs  max=1.72ms  p(95)=23.68µs  p(99)=32.2µs  
     http_req_tls_handshaking.......: min=0s       avg=0s       med=0s       max=0s      p(95)=0s       p(99)=0s      
     http_req_waiting...............: min=279.12µs avg=370.18µs med=344.18µs max=25.19ms p(95)=440.79µs p(99)=538.44µs
     http_reqs......................: 60001   999.998231/s
     ✓ { scenario:rps_1000 }........: 60001   999.998231/s
     iteration_duration.............: min=388.99µs avg=500.33µs med=471.71µs max=25.53ms p(95)=575.29µs p(99)=752.43µs
     iterations.....................: 60001   999.998231/s
     ✓ { scenario:rps_1000 }........: 60001   999.998231/s
     valid_graphql_response.........: 100.00% ✓ 60001      ✗ 0    
     ✓ { scenario:rps_1000 }........: 100.00% ✓ 60001      ✗ 0    
     valid_http_code................: 100.00% ✓ 60001      ✗ 0    
     ✓ { scenario:rps_1000 }........: 100.00% ✓ 60001      ✗ 0    
     vus............................: 0       min=0        max=2  
     vus_max........................: 200     min=200      max=200

@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.31.0 chore(deps): update dependency wrangler to v3.32.0 Mar 7, 2024
@renovate renovate bot changed the title chore(deps): update dependency wrangler to v3.32.0 chore(deps): update dependency wrangler to v3.33.0 Mar 12, 2024
@dotansimha dotansimha merged commit 6d7e668 into master Mar 13, 2024
14 checks passed
@renovate renovate bot deleted the renovate/wrangler-3.x branch March 13, 2024 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant