api icon indicating copy to clipboard operation
api copied to clipboard

Published 20 hours ago • verified publisher icon wanderer-moe

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

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

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

v3.114.8

Compare Source

Patch Changes

  • #​9086 a2a56c8 Thanks @​petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

    Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.

  • #​9037 d0d0025 Thanks @​CarmenPopoviciu! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.

  • #​9093 2f2f7ba Thanks @​CarmenPopoviciu! - fix: Validate input file for Vectorize inserts

  • Updated dependencies [fc04292, a01adca]:

v3.114.7

Compare Source

Patch Changes

  • #​8955 b7eba92 Thanks @​workers-devprod! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.

  • #​8928 8bcb257 Thanks @​dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

v3.114.6

Compare Source

Patch Changes

  • #​8783 7bcf352 Thanks @​petebacondarwin! - Improve error message when request to obtain membership info fails

    Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.

  • #​8866 db673d6 Thanks @​edmundhung! - improve error message when redirected config contains environments

    this change improves that validation error message that users see when a redirected config file contains environments, by:

    • cleaning the message formatting and displaying the offending environments in a list
    • prompting the user to report the issue to the author of the tool which has generated the config

  • #​8600 91cf028 Thanks @​workers-devprod! - add validation to redirected configs in regards to environments

    add the following validation behaviors to wrangler deploy commands, that relate to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):

    • redirected configs are supposed to be already flattened configurations without any environment (i.e. a build tool should generate redirected configs already targeting specific environments), so if wrangler encounters a redirected config with some environments defined it should error
    • given the point above, specifying an environment (--env=my-env) when using redirected configs is incorrect, so these environments should be ignored and a warning should be presented to the user

v3.114.5

Compare Source

Patch Changes

v3.114.4

Compare Source

Patch Changes

v3.114.3

Compare Source

Patch Changes

v3.114.2

Compare Source

Patch Changes

v3.114.1

Compare Source

Patch Changes

  • #​8383 8d6d722 Thanks @​matthewdavidrodgers! - Make kv bulk put --local respect base64:true

    The bulk put api has an optional "base64" boolean property for each key. Before storing the key, the value should be decoded from base64.

    For real (remote) kv, this is handled by the rest api. For local kv, it seems the base64 field was ignored, meaning encoded base64 content was stored locally rather than the raw values.

    To fix, we need to decode each value before putting to the local miniflare namespace when base64 is true.

  • #​8273 e3efd68 Thanks @​penalosa! - Support AI, Vectorize, and Images bindings when using @cloudflare/vite-plugin

  • #​8427 a352798 Thanks @​vicb! - update unenv-preset dependency to fix bug with Performance global

    Fixes #​8407 Fixes #​8409 Fixes #​8411

  • #​8390 53e6323 Thanks @​GregBrimble! - Parse and apply metafiles (_headers and _redirects) in wrangler dev for Workers Assets

  • #​8392 4d9d9e6 Thanks @​jahands! - fix: retry zone and route lookup API calls

    In rare cases, looking up Zone or Route API calls may fail due to transient errors. This change improves the reliability of wrangler deploy when these errors occur.

    Also fixes a rare issue where concurrent API requests may fail without correctly throwing an error which may cause a deployment to incorrectly appear successful.

  • Updated dependencies [8242e07, 53e6323]:

v3.114.0

Compare Source

Minor Changes

v3.113.0

Compare Source

Minor Changes
Patch Changes

  • #​8338 2d40989 Thanks @​GregBrimble! - feat: Upload _headers and _redirects if present with Workers Assets as part of wrangler deploy and wrangler versions upload.

  • #​8288 cf14e17 Thanks @​CarmenPopoviciu! - feat: Add assets Proxy Worker skeleton in miniflare

    This commit implements a very basic Proxy Worker skeleton, and wires it in the "pipeline" miniflare creates for assets. This Worker will be incrementally worked on, but for now, the current implementation will forward all incoming requests to the Router Worker, thus leaving the current assets behaviour in local dev, the same.

    This is an experimental feature available under the --x-assets-rpc flag: wrangler dev --x-assets-rpc.

  • #​8216 af9a57a Thanks @​ns476! - Support Images binding in wrangler types

  • #​8304 fbba583 Thanks @​jahands! - chore: add concurrency and caching for Zone IDs and Workers routes lookups

    Workers with many routes can result in duplicate Zone lookups during deployments, making deployments unnecessarily slow. This compounded by the lack of concurrency when making these API requests.

    This change deduplicates these requests and adds concurrency to help speed up deployments.

  • Updated dependencies [2d40989, da568e5, cf14e17, 79c7810]:

v3.112.0

Compare Source

Minor Changes

  • #​8256 f59d95b Thanks @​jbwcloudflare! - Add two new Queues commands: pause-delivery and resume-delivery

    These new commands allow users to pause and resume the delivery of messages to Queue Consumers

Patch Changes

v3.111.0

Compare Source

Minor Changes
Patch Changes

v3.110.0

Compare Source

Minor Changes
Patch Changes

v3.109.3

Compare Source

Patch Changes

v3.109.2

Compare Source

Patch Changes

v3.109.1

Compare Source

Patch Changes

v3.109.0

Compare Source

Minor Changes

  • #​8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

  • #​8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

  • #​8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

    This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

  • #​8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

    This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

    Advanced usage:

    • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
    • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/
Patch Changes

v3.108.1

Compare Source

Patch Changes

v3.108.0

Compare Source

Minor Changes
Patch Changes

  • #​8058 1f80d69 Thanks @​WillTaylorDev! - Bugfix: Modified versions secret put to inherit all known bindings, which circumvents a limitation in the API which does not return all fields for all bindings.

  • #​7986 88514c8 Thanks @​andyjessop! - docs: clarifies that local resources are "simulated locally" or "connected to remote resource", and adds console messages to help explain local dev

  • #​8008 9d08af8 Thanks @​ns476! - Add support for Images bindings (in private beta for now), with optional local support for platforms where Sharp is available.

  • #​7769 6abe69c Thanks @​cmackenzie1! - Adds the following new option for wrangler pipelines create and wrangler pipelines update commands:

    --cors-origins           CORS origin allowlist for HTTP endpoint (use * for any origin)  [array]

  • #​7290 0c0374c Thanks @​emily-shen! - fix: add support for workers with assets when running multiple workers in one wrangler dev instance

    https://github.com/cloudflare/workers-sdk/pull/7251 added support for running multiple Workers in one wrangler dev/miniflare session. e.g. wrangler dev -c wrangler.toml -c ../worker2/wrangler.toml, which among other things, allowed cross-service RPC to Durable Objects.

    However this did not work in the same way as production when there was a Worker with assets - this PR should fix that.

  • #​7769 6abe69c Thanks @​cmackenzie1! - Rename wrangler pipelines <create|update> flags

    The following parameters have been renamed:

    Previous Name New Name
    access-key-id r2-access-key-id
    secret-access-key r2-secret-access-key
    transform transform-worker
    r2 r2-bucket
    prefix r2-prefix
    binding enable-worker-binding
    http enable-http
    authentication require-http-auth
    filename file-template
    filepath partition-template

  • #​8012 c412a31 Thanks @​mtlemilio! - Use fetchPagedListResult when listing Hyperdrive configs from the API

    This fixes an issue where only 20 configs were being listed.

  • #​8077 60310cd Thanks @​emily-shen! - feat: add telemetry to experimental auto-provisioning

  • Updated dependencies [c80dbd8, 0c0374c]:

v3.107.3

Compare Source

Patch Changes

v3.107.2

Compare Source

Patch Changes

v3.107.1

Compare Source

Patch Changes

v3.107.0

Compare Source

Minor Changes
Patch Changes

  • #​7945 d758215 Thanks @​ns476! - Add Images binding (in private beta for the time being)

  • #​7947 f57bc4e Thanks @​dario-piotrowicz! - fix: avoid getPlatformProxy logging twice that it is using vars defined in .dev.vars files

    when getPlatformProxy is called and it retrieves values from .dev.vars files, it logs twice a message like: Using vars defined in .dev.vars, the changes here make sure that in such cases this log only appears once

  • #​7889 38db4ed Thanks @​emily-shen! - feat: add experimental resource auto-provisioning to versions upload

  • #​7864 de6fa18 Thanks @​dario-piotrowicz! - Update the unstable_getMiniflareWorkerOptions types to always include an env parameter.

    The unstable_getMiniflareWorkerOptions types, when accepting a config object as the first argument, didn't accept a second env argument. The changes here make sure they do, since the env is still relevant for picking up variables from .dev.vars files.

  • #​7964 bc4d6c8 Thanks @​LuisDuarte1! - Fix scripts binding to a workflow in a different script overriding workflow config

  • Updated dependencies [cf4f47a]:

v3.106.0

Compare Source

Minor Changes

  • #​7856 2b6f149 Thanks @​emily-shen! - feat: add sanitised error messages to Wrangler telemetry

    Error messages that have been audited for potential inclusion of personal information, and explicitly opted-in, are now included in Wrangler's telemetry collection. Collected error messages will not include any filepaths, user input or any other potentially private content.

  • #​7900 bd9228e Thanks @​vicb! - chore(wrangler): update unenv dependency version

    [email protected] allows using the workerd implementation for the Node modules net, timers, and timers/promises. See unjs/unenv#396.

Patch Changes

  • #​7904 50b13f6 Thanks @​WalshyDev! - fix: validation for R2 bucket names, the regex was wrongly rejecting buckets starting with a number and the message wasn't as clear as it could be on what was going wrong.

  • #​7895 134d61d Thanks @​jahands! - Fix regression in retryOnAPIFailure preventing any requests from being retried

    Also fixes a regression in pipelines that prevented 401 errors from being retried when waiting for an API token to become active.

  • #​7879 5c02e46 Thanks @​andyjessop! - Fix to not require local connection string when using Hyperdrive and wrangler dev --remote

  • #​7860 13ab591 Thanks @​vicb! - refactor(wrangler): make JSON parsing independent of Node

    Switch jsonc-parser to parse json:

    • JSON.parse() exception messages are not stable across Node versions
    • While jsonc-parser is used, JSONC specific syntax is disabled

  • Updated dependencies []:

v3.105.1

Compare Source

Patch Changes

v3.105.0

Compare Source

Minor Changes

  • #​7466 e5ebdb1 Thanks @​Ltadrian! - feat: implement the wrangler cert upload command

    This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

    For uploading mTLS certificate, run:

    • wrangler cert upload mtls-certificate --cert cert.pem --key key.pem --name MY_CERT

    For uploading CA certificate chain, run:

    • wrangler cert upload certificate-authority --ca-cert server-ca.pem --name SERVER_CA
Patch Changes

v3.104.0

Compare Source

Minor Changes

  • #​7715 26fa9e8 Thanks @​penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

  • #​7816 f6cc029 Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

    this change makes sure that that getPlatformProxy, when the input configuration file contains an assets field, correctly returns the appropriate asset binding proxy

    example:

    // wrangler.json
{
	"name": "my-worker",
	"assets": {
		"directory": "./public/",
		"binding": "ASSETS"
	},
	"vars": {
		"MY_VAR": "my-var"
	}
}

    import { getPlatformProxy } from "wrangler";

const { env, dispose } = await getPlatformProxy();

if (env.ASSETS) {
	const text = await (
		await env.ASSETS.fetch("http://0.0.0.0/file.txt")
	).text();
	console.log(text); // logs the content of file.txt
}

await dispose();
Patch Changes

v3.103.2

Compare Source

Patch Changes

v3.103.1

Compare Source

Patch Changes

v3.103.0

Compare Source

Minor Changes

  • #​5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

    add a new --strict-vars option to wrangler types that developers can (by setting the flag to false) use to disable the default strict/literal types generation for their variables

    opting out of strict variables can be useful when developers change often their vars values, even more so when multiple environments are involved

v3.102.0

Compare Source

Minor Changes
Patch Changes

v3.101.0

Compare Source

Minor 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 Apr 24 '24 14:04 renovate[bot]