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

build(deps-dev): bump wrangler from 2.21.2 to 3.82.0 in /examples/cloudflare-workers #1331

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 22, 2024

Bumps wrangler from 2.21.2 to 3.82.0.

Release notes

Sourced from wrangler's releases.

wrangler@3.82.0

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

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.82.0

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

... (truncated)

Commits
  • 8d03647 Version Packages (#7019)
  • 9bf51d6 Validate duplicate bindings across all binding types (#5737)
  • e1b93dc fix: ask for confirmation before creating a new worker when uploading secrets...
  • 6131ef5 fix(wrangler): enforce single value on non-array arguments (#7005)
  • 6b97353 Add jurisdiction option to R2 event notification wrangler actions (#6945)
  • 127615a fix: log successful execution of D1 commands locally (#7018)
  • 045787b fix(wrangler): Show wrangler pages dev --proxy warning (#7041)
  • f9d5fdb PIPE-37 Small API restructuring for Worker Pipelines (#7046)
  • a8ca700 PIPE-37 Add authenticated HTTP source options to Worker Pipelines (#6970)
  • e44f496 Only show dev registry connection status in local dev (#7039)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) from 2.21.2 to 3.82.0.
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@3.82.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 22, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 24, 2024

Superseded by #1335.

@dependabot dependabot bot closed this Oct 24, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/examples/cloudflare-workers/wrangler-3.82.0 branch October 24, 2024 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants