fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #99 · biomejs/discord-utils-bot

renovate · 2025-01-20T00:58:27Z

This PR contains the following updates:

Package	Change	Type	Update
@cloudflare/workers-types	`^4.20241230.0` -> `^4.20250121.0`	devDependencies	minor
cloudflare/wrangler-action	`v3.13.0` -> `v3.13.1`	action	patch
discord-api-types (source)	`^0.37.115` -> `^0.37.117`	dependencies	patch
pnpm (source)	`9.15.3` -> `9.15.4`	packageManager	patch
typescript (source)	`^5.7.2` -> `^5.7.3`	devDependencies	patch
wrangler (source)	`^3.100.0` -> `^3.105.0`	devDependencies	minor

Release Notes

cloudflare/workerd (@cloudflare/workers-types)

`v4.20250121.0`

Compare Source

`v4.20250109.0`

Compare Source

cloudflare/wrangler-action (cloudflare/wrangler-action)

`v3.13.1`

Compare Source

Patch Changes

#345 e819570 Thanks @Maximo-Guk! - fix: Pages GitHub Deployment not triggering

discordjs/discord-api-types (discord-api-types)

`v0.37.117`

Compare Source

`v0.37.116`

Compare Source

Features

VoiceCloseCodes: add BadRequest (#1191) (d9b6935)

pnpm/pnpm (pnpm)

`v9.15.4`: pnpm 9.15.4

Compare Source

Patch Changes

Ensure that recursive pnpm update --latest <pkg> updates only the specified package, with dedupe-peer-dependents=true.

Platinum Sponsors

Gold Sponsors

microsoft/TypeScript (typescript)

`v5.7.3`

Compare Source

cloudflare/workers-sdk (wrangler)

`v3.105.0`

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

#7867 bdc7958 Thanks @penalosa! - Revert https://github.com/cloudflare/workers-sdk/pull/7816. This feature added support for the ASSETS bindings to the getPlatformProxy() API, but caused a regression when running npm run preview in newly generated Workers Assets projects.
#7868 78a9a2d Thanks @penalosa! - Revert "Hyperdrive dev remote fix". This PR includes e2e tests that were not run before merging, and are currently failing.
Updated dependencies []:
- miniflare@3.20241230.2

`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

#7785 cccfe51 Thanks @joshthoward! - Fix Durable Objects transfer migration validation
#7821 fcaa02c Thanks @vicb! - fix(wrangler): fix wrangler config schema defaults
#7832 97d2a1b Thanks @petebacondarwin! - Relax the messaging when Wrangler uses redirected configuration

Previously the messaging was rendered as a warning, which implied that the user
had done something wrong. Now it is just a regular info message.
#7806 d7adb50 Thanks @vicb! - chore: update unenv to 2.0.0-rc.0

Pull a couple changes in node:timers
- unjs/unenv#384 fix function bindings in node:timer
- unjs/unenv#385 implement active and _unrefActive in node:timer
The unenv update also includes #unjs/unenv/381 which implements
stdout, stderr and stdin of node:process with node:tty
#7828 9077a67 Thanks @edmundhung! - improve multi account error message in non-interactive mode
Updated dependencies []:
- miniflare@3.20241230.2

`v3.103.2`

Compare Source

Patch Changes

#7804 16a9460 Thanks @vicb! - fix(wrangler): use require.resolve to resolve unenv path

`v3.103.1`

Compare Source

Patch Changes

#7798 a1ff045 Thanks @CarmenPopoviciu! - Reverts #7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)

`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

#7592 f613276 Thanks @garrettgu10! - New filter validation logic supporting set and range queries in Vectorize CLI

Patch Changes

#7750 df0e5be Thanks @andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output of wrangler dev, and adds-in the same tag for Durable Objects (which are emulated locally in wrangler dev).
#7732 d102b60 Thanks @Ankcorn! - fix pages secret bulk copy
#7706 c63f1b0 Thanks @penalosa! - Remove the server-based dev registry in favour of the more stable file-based dev registry. There should be no user-facing impact.
Updated dependencies [8e9aa40]:
- miniflare@3.20241230.2

`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

#7456 ff4e77e Thanks @andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.
#7712 6439347 Thanks @penalosa! - Remove CF-Connecting-IP for requests to the edge preview
#7703 e771fe9 Thanks @petebacondarwin! - include the top level Worker name in the parsed config structure
#7576 773bda8 Thanks @cmackenzie1! - Remove defaults for batch-max-* pipeline parameters and define value ranges
Updated dependencies [2c76887, 78bdec5]:
- miniflare@3.20241230.1

Configuration

📅 Schedule: Branch creation - "before 9am on monday" in timezone Europe/Gibraltar, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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 force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7d6a925 to 967f2b5 Compare January 22, 2025 10:13

fix(deps): update all non-major dependencies

a8c72ab

renovate bot force-pushed the renovate/all-minor-patch branch from 967f2b5 to a8c72ab Compare January 22, 2025 21:10

SuperchupuDev merged commit 60d251e into main Jan 22, 2025
2 checks passed

SuperchupuDev deleted the renovate/all-minor-patch branch January 22, 2025 21:37

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update all non-major dependencies#99

fix(deps): update all non-major dependencies#99
SuperchupuDev merged 1 commit intomainfrom
renovate/all-minor-patch

renovate bot commented Jan 20, 2025 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate bot commented Jan 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Features

v9.15.4: pnpm 9.15.4

Patch Changes

Platinum Sponsors

Gold Sponsors

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Affected commands

Config redirect file

Custom build tool example

Patch Changes

Configuration

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Jan 20, 2025 •

edited

Loading

`v9.15.4`: pnpm 9.15.4