chore: bump up all non-major dependencies #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.20241230.0
->4.20250121.0
^0.0.16
->^0.0.19
22.10.5
->22.10.10
9.15.2
->9.15.4
6.1.70
->6.1.74
5.7.2
->5.7.3
3.99.0
->3.105.0
Release Notes
cloudflare/workerd (@cloudflare/workers-types)
v4.20250121.0
Compare Source
v4.20250109.0
Compare Source
oxc-project/oxc-node (@oxc-node/core)
v0.0.19
Compare Source
Note: Version bump only for package oxc-node
v0.0.18
Compare Source
Bug Fixes
v0.0.17
Compare Source
Bug Fixes
pnpm/pnpm (pnpm)
v9.15.4
: pnpm 9.15.4Compare Source
Patch Changes
pnpm update --latest <pkg>
updates only the specified package, withdedupe-peer-dependents=true
.Platinum Sponsors
Gold Sponsors
v9.15.3
Compare Source
remusao/tldts (tldts)
v6.1.74
Compare Source
📜 Update Public Suffix List
tldts-experimental
,tldts-icann
,tldts
🔩 Dependencies
Authors: 2
v6.1.73
Compare Source
📜 Update Public Suffix List
tldts-experimental
,tldts
🔩 Dependencies
Authors: 2
v6.1.72
Compare Source
📜 Update Public Suffix List
tldts-experimental
,tldts-icann
,tldts-tests
,tldts
🔩 Dependencies
Authors: 2
v6.1.71
Compare Source
📜 Update Public Suffix List
tldts-experimental
,tldts
🔩 Dependencies
Authors: 2
microsoft/TypeScript (typescript)
v5.7.3
Compare Source
cloudflare/workers-sdk (wrangler)
v3.105.0
Compare Source
Minor Changes
#7466
e5ebdb1
Thanks @Ltadrian! - feat: implement thewrangler cert upload
commandThis 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 thegetPlatformProxy()
API, but caused a regression when runningnpm 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 []:
v3.104.0
Compare Source
Minor Changes
#7715
26fa9e8
Thanks @penalosa! - Support service bindings from Pages projects to Workers in a singleworkerd
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 togetPlatformProxy
this change makes sure that that
getPlatformProxy
, when the input configurationfile contains an assets field, correctly returns the appropriate asset binding proxy
example:
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 configurationPreviously 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.0Pull a couple changes in node:timers
The unenv update also includes #unjs/unenv/381 which implements
stdout
,stderr
andstdin
ofnode:process
withnode:tty
#7828
9077a67
Thanks @edmundhung! - improve multi account error message in non-interactive modeUpdated dependencies []:
v3.103.2
Compare Source
Patch Changes
16a9460
Thanks @vicb! - fix(wrangler): use require.resolve to resolve unenv pathv3.103.1
Compare Source
Patch Changes
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 towrangler types
add a new
--strict-vars
option towrangler types
that developers can (by setting theflag to
false
) use to disable the default strict/literal types generation for their variablesopting 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
f613276
Thanks @garrettgu10! - New filter validation logic supporting set and range queries in Vectorize CLIPatch Changes
#7750
df0e5be
Thanks @andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output ofwrangler dev
, and adds-in the same tag for Durable Objects (which are emulated locally inwrangler 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
]: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 fileThis 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 commandsThis 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: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.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:The
dist/wrangler.json
will contain:And the
.wrangler/deploy/config.json
will contain:#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 failingPatch 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 forbatch-max-*
pipeline parameters and define value rangesUpdated dependencies [
2c76887
,78bdec5
]:v3.100.0
Compare Source
Minor Changes
#7604
6c2f173
Thanks @CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry dataWe 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 versionunenv now uses the workerd implementation on node:dns
See the unjs/unenv#376
#7625
d8fb032
Thanks @vicb! - feat(wrangler): use unenv builtin dependency resolutionMoving 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 versionThe 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.