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

Update dependency wrangler to v3.105.1 #10

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

Update dependency wrangler to v3.105.1 #10

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2025 •
edited
Loading

This PR contains the following updates:

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

Release Notes

cloudflare/workers-sdk (wrangler)

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

  • #​7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

  • #​7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

    Run wrangler secret bulk .dev.vars to add the env file

    //.dev.vars
KEY=VALUE
KEY_2=VALUE

    This will upload the secrets KEY and KEY_2 to your worker

  • #​7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

    This new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
    which Wrangler can use instead of user configuration when running deploy-related commands.
    It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:

  • wrangler deploy
  • wrangler dev
  • wrangler versions upload
  • wrangler versions deploy
  • wrangler pages deploy
  • wrangler pages build
  • wrangler pages build-env
Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

{ "configPath": "../../path/to/wrangler.json" }

When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.

  • The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.

    name = "my-worker"
main = "src/index.ts"
[[kv_namespaces]]
binding = "<BINDING_NAME1>"
id = "<NAMESPACE_ID1>"

    Note that this configuration points main at user code entry-point.

  • The user runs a custom build, which might read the wrangler.toml to find the entry-point:

    > my-tool build

  • This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:

    - dist
  - index.js
	- wrangler.json
- .wrangler
  - deploy
	  - config.json

    The dist/wrangler.json will contain:

    {
  "name": "my-worker",
  "main": "./index.js",
  "kv_namespaces": [
    { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
  ]
}

    And the .wrangler/deploy/config.json will contain:

    {
  "configPath": "../../dist/wrangler.json"
}

  • #​7685 9d2740a Thanks @​vicb! - allow overriding the unenv preset.

    By default wrangler uses the bundled unenv preset.

    Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
    Those paths are used when resolving the unenv module identifiers to absolute paths.
    This can be used to test a development version.

  • #​7694 f3c2f69 Thanks @​joshthoward! - Default wrangler d1 export to --local rather than failing

Patch Changes

v3.100.0

Compare Source

Minor Changes

  • #​7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

    We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

    These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

    N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

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

    unenv now uses the workerd implementation on node:dns
    See the unjs/unenv#376

  • #​7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

    Moving away from require.resolve() to handle unenv aliased packages.
    Using the unenv builtin resolution will allow us to drop the .cjs file from the preset
    and to override the base path so that we can test the dev version of the preset.

  • #​7533 755a27c Thanks @​danielgek! - Add warning about the browser rendering not available on local

  • #​7614 8abb43f Thanks @​vicb! - chore(wrangler): update unenv dependency version

    The updated unenv contains a fix for the module resolution,
    see unjs/unenv#378.
    That bug prevented us from using unenv module resolution,
    see #​7583.

  • Updated dependencies [b4e0af1]:

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.

@sourcery-ai Sourcery AI
Copy link

sourcery-ai bot commented Jan 8, 2025 •
edited
Loading

Reviewer's Guide by Sourcery

This pull request updates the wrangler dependency from version 3.99.0 to 3.100.0, reflecting changes in the pnpm-lock.yaml and package.json files to ensure compatibility with the latest features and fixes provided in the new version.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Update wrangler dependency to version 3.100.0
  • Updated wrangler version from 3.99.0 to 3.100.0 in pnpm-lock.yaml
  • Updated wrangler version from 3.99.0 to 3.100.0 in package.json
 pnpm-lock.yaml
package.json

Possibly linked issues

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

sourcery-ai[bot]
sourcery-ai bot reviewed Jan 8, 2025
View reviewed changes
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from a905342 to c4261d7 Compare January 10, 2025 05:51
@renovate renovate bot changed the title Update dependency wrangler to v3.100.0 Update dependency wrangler to v3.101.0 Jan 10, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from c4261d7 to 67d5126 Compare January 15, 2025 05:57
@renovate renovate bot changed the title Update dependency wrangler to v3.101.0 Update dependency wrangler to v3.102.0 Jan 15, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 67d5126 to 57c32db Compare January 17, 2025 03:37
@renovate renovate bot changed the title Update dependency wrangler to v3.102.0 Update dependency wrangler to v3.103.1 Jan 17, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 57c32db to c6f2d31 Compare January 20, 2025 06:19
@renovate renovate bot changed the title Update dependency wrangler to v3.103.1 Update dependency wrangler to v3.103.2 Jan 20, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch 2 times, most recently from af08881 to 94cc3d5 Compare January 23, 2025 05:42
@renovate renovate bot changed the title Update dependency wrangler to v3.103.2 Update dependency wrangler to v3.105.0 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/wrangler-3.x branch from 94cc3d5 to 4dc8bf3 Compare January 25, 2025 07:28
@renovate renovate bot changed the title Update dependency wrangler to v3.105.0 Update dependency wrangler to v3.105.1 Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

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