Skip to content
Cloudflare Docs

Wrangler

2024-09-18

3.78.5

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

2024-09-17

3.78.4

Patch Changes

  • #6706 1c42466 Thanks @jkoe-cf! - fix: making explicit to only send a body if there are rule ids specified in the config delete

  • #6714 62082aa Thanks @OilyLime! - fix: rough edges when creating and updating Hyperdrive over Access configs

  • #6705 ea60a52 Thanks @emily-shen! - fix: include compatability date in static-asset only uploads (experimental feature)

2024-09-13

3.78.2

Patch Changes

3.78.1

Patch Changes

3.78.0

Minor Changes

  • #6643 f30c61f Thanks @WalshyDev! - feat: add "Deployment alias URL" to wrangler pages deploy if an alias is available for this deployment.

  • #6415 b27b741 Thanks @irvinebroque! - chore: Redirect wrangler generate [template name] and wrangler init to npm create cloudflare

  • #6647 d68e8c9 Thanks @joshthoward! - feat: Configure SQLite backed Durable Objects in local dev

  • #6696 0a9e90a Thanks @penalosa! - feat: Support WRANGLER_CI_MATCH_TAG environment variable.

    When set, this will ensure that wrangler deploy and wrangler versions upload only deploy to Workers which match the provided tag.

  • #6702 aa603ab Thanks @hhoughgg! - feat: Hide wrangler pipelines until release

Patch Changes

2024-09-12

3.77.0

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

  • #6621 6523db2 Thanks @emily-shen! - fix: Validate routes in wrangler dev and wrangler deploy for Workers with assets

    We want wrangler to error if users are trying to deploy a Worker with assets, and routes with a path component.

    All Workers with assets must have either:

    • custom domain routes
    • pattern routes which have no path component (except for the wildcard splat) "some.domain.com/*"

  • #6687 7bbed63 Thanks @GregBrimble! - fix: Fix asset upload count messaging

  • #6628 33cc0ec Thanks @GregBrimble! - chore: Improves messaging when uploading assets

  • #6671 48eeff4 Thanks @jkoe-cf! - fix: Update R2 Create Event Notification response

  • #6618 67711c2 Thanks @GregBrimble! - fix: Switch to multipart/form-data upload format for Workers Assets

    This has proven to be much more reliable.

  • Updated dependencies [3f5b934, 59a0072]:

2024-09-10

3.76.0

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

  • #6612 6471090 Thanks @dario-piotrowicz! - fix: Add hyperdrive binding support in getPlatformProxy

    example:

    # wrangler.toml
[[hyperdrive]]
binding = "MY_HYPERDRIVE"
id = "000000000000000000000000000000000"
localConnectionString = "postgres://user:pass@127.0.0.1:1234/db"

    // index.mjs

import postgres from "postgres";
import { getPlatformProxy } from "wrangler";

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

try {
  const sql = postgres(
    // Note: connectionString points to `postgres://user:pass@127.0.0.1:1234/db` not to the actual hyperdrive
    //       connection string, for more details see the explanation below
    env.MY_HYPERDRIVE.connectionString,
  );
  const results = await sql`SELECT * FROM pg_tables`;
  await sql.end();
} catch (e) {
  console.error(e);
}

await dispose();

    Note: the returned binding values are no-op/passthrough that can be used inside node.js, meaning that besides direct connections via the connect methods, all the other values point to the same db connection specified in the user configuration

  • #6620 ecdfabe Thanks @petebacondarwin! - fix: don't warn about node:async_hooks if nodejs_als is set

    Fixes #6011

  • Updated dependencies [5936282, 6471090]:

Cloudflare DashboardDiscordCommunityLearning CenterSupport Portal