This repository has been archived by the owner on Apr 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update dependency wrangler to v3 #8
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/wrangler-3.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
June 6, 2023 21:03
2c3581b
to
55871e5
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
June 20, 2023 20:10
55871e5
to
a24b1a2
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
2 times, most recently
from
July 11, 2023 22:45
cb65443
to
28047ec
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
July 18, 2023 18:31
28047ec
to
ef79dce
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
July 27, 2023 18:57
ef79dce
to
d535475
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
August 8, 2023 19:06
d535475
to
4fca4f6
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
August 15, 2023 21:52
4fca4f6
to
d6df2d1
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
August 24, 2023 17:34
d6df2d1
to
c8627b4
Compare
renovate
bot
changed the title
chore(deps): update dependency wrangler to v3
chore(deps): update dependency wrangler to v3 - autoclosed
Aug 28, 2023
renovate
bot
changed the title
chore(deps): update dependency wrangler to v3 - autoclosed
chore(deps): update dependency wrangler to v3
Aug 28, 2023
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
August 28, 2023 21:35
c8627b4
to
eda3968
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
September 5, 2023 19:38
eda3968
to
5c503eb
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
2 times, most recently
from
September 20, 2023 16:42
b443dbc
to
c83ef42
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
3 times, most recently
from
September 28, 2023 20:00
8d3849d
to
71dfdc0
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
3 times, most recently
from
October 12, 2023 18:37
68107ec
to
fec467a
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
3 times, most recently
from
October 17, 2023 22:31
481179b
to
c808de9
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
October 19, 2023 22:25
c808de9
to
28ebff7
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
2 times, most recently
from
February 6, 2024 21:57
97c0a7d
to
52bf9bf
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
3 times, most recently
from
February 13, 2024 19:13
22287e7
to
5955710
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
3 times, most recently
from
February 22, 2024 23:04
28ad275
to
91a6d84
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
3 times, most recently
from
March 5, 2024 19:10
fa423d3
to
723cdd8
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
5 times, most recently
from
March 14, 2024 17:14
9431cc0
to
15836c6
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
4 times, most recently
from
March 26, 2024 19:21
a9c0280
to
f0507a6
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
6 times, most recently
from
April 2, 2024 22:59
325ee14
to
5adb78b
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
2 times, most recently
from
April 5, 2024 02:05
7fff770
to
a4c42ac
Compare
renovate
bot
force-pushed
the
renovate/wrangler-3.x
branch
from
April 5, 2024 19:39
a4c42ac
to
16a8379
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
2.8.1
->3.48.0
Release Notes
cloudflare/workers-sdk (wrangler)
v3.48.0
Compare Source
Minor Changes
#5429
c5561b7
Thanks @ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it isenabled on your account.
Wrangler supports an
-s
flag that allows the user to specify a storage class when creating a bucket,changing the default storage class of a bucket, and uploading an object.
Patch Changes
#5531
887150a
Thanks @penalosa! - fix: Writewrangler pages functions build-env
to file rather than stdout#5526
bafbd67
Thanks @rozenmd! - fix: teachwrangler d1 create
about Australiav3.47.1
Compare Source
Patch Changes
9f15ce1
]:v3.47.0
Compare Source
Minor Changes
7734f80
Thanks @penalosa! - feat: Add interactive prompt towrangler pages download config
if an existingwrangler.toml
file existsv3.46.0
Compare Source
Minor Changes
#5282
b7ddde1
Thanks @maxwellpeterson! - feature: Add source map support for WorkersAdds the
source_maps
boolean config option. When enabled, source maps included in the build output are uploaded alongside the built code modules. Uploaded source maps can then be used to remap stack traces emitted by the Workers runtime.#5215
cd03d1d
Thanks @GregBrimble! - feature: support named entrypoints in service bindingsThis change allows service bindings to bind to a named export of another Worker. As an example, consider the following Worker named
bound
:Up until now, you could only bind to the
default
entrypoint. With this change, you can bind toEntrypointA
orentrypointB
too using the newentrypoint
option:To bind to named entrypoints with
wrangler pages dev
, use the#
character:Patch Changes
#5215
cd03d1d
Thanks @GregBrimble! - fix: ensure requesturl
andcf
properties preserved across service bindingsPreviously, Wrangler could rewrite
url
andcf
properties when sending requests via service bindings or Durable Object stubs. To match production behaviour, this change ensures these properties are preserved.Updated dependencies [
cd03d1d
,6c3be5b
,cd03d1d
,cd03d1d
]:v3.45.0
Compare Source
Minor Changes
#5377
5d68744
Thanks @CarmenPopoviciu! - feat: Addwrangler.toml
support inwrangler pages deploy
As we are adding
wrangler.toml
support for Pages, we want to ensure thatwrangler pages deploy
works with a configuration file.#5471
489b9c5
Thanks @zebp! - feature: Add version-id filter for Worker tailing to filter logs by scriptVersion in a gradual deploymentThis allows users to only get logs in a gradual deployment if you are troubleshooting issues
specific to one deployment. Example:
npx wrangler tail --version-id 72d3f357-4e52-47c5-8805-90be978c403f
Patch Changes
#5462
68faf67
Thanks @OilyLime! - revert: Removes support for private networking Hyperdrive configs, pending more work to support the feature. Non-breaking change since the feature wasn't yet supported.#5494
a232ccf
Thanks @penalosa! - fix: Swallow parsing errors when a pages config file is required.#5484
e7f8dc3
Thanks @ichernetsky-cf! - feature: support Cloudchamber deployment labels#5434
bf9dca8
Thanks @OilyLime! - bugfix: Fix passing Hyperdrive caching options to backend#5403
5d6d521
Thanks @oliy! - fix: wrangler dev --local support for ratelimitsUpdated dependencies [
940ad89
]:v3.44.0
Compare Source
Minor Changes
#5461
f69e562
Thanks @mattdeboard! - feature: Add command for fetching R2 Event Notification configurations for a given bucketThis allows users to see the entire event notification configuration -- i.e. every rule for every configured queue -- for a single bucket with a single request.
This change also improves messaging of console output when creating a new bucket notification.
Patch Changes
#5480
0cce21f
Thanks @penalosa! - fix: Ensure url & node:url export URL (aliased to globalThis.URL) in node_compat mode#5472
02a1091
Thanks @penalosa! - fix: Expose more info fromwrangler pages functions build-env
v3.43.0
Compare Source
Minor Changes
ef9fbba
Thanks @celso! - feature: add Workers AI finetune commandsPatch Changes
91a2150
Thanks @penalosa! - fix: Improve messaging for invalid Pageswrangler.toml
filesv3.42.0
Compare Source
Minor Changes
#5371
77152f3
Thanks @G4brym! - feature: remove requirement for@cloudflare/ai
package to use Workers AIPreviously, to get the correct Workers AI API, you needed to wrap your
env.AI
binding withnew Ai()
from@cloudflare/ai
. This change moves the contents of@cloudflare/ai
into the Workers runtime itself, meaningenv.AI
is now an instance ofAi
, without the need for wrapping.Patch Changes
d994066
]:v3.41.0
Compare Source
Minor Changes
b7a6d9d
Thanks @rozenmd! - feat: implementwrangler d1 export
v3.40.0
Compare Source
Minor Changes
#5426
9343714
Thanks @RamIdeas! - feature: added a newwrangler triggers deploy
commandThis command currently requires the
--experimental-versions
flag.This command extracts the trigger deployment logic from
wrangler deploy
and allows users to update their currently deployed Worker's triggers without doing another deployment. This is primarily useful for users ofwrangler versions upload
andwrangler versions deploy
who can then runwrangler triggers deploy
to apply trigger changes to their currently deployed Worker Versions.The command can also be used even if not using the
wrangler versions ...
commands. And, in fact, users are already using it implicitly when runningwrangler deploy
.#4932
dc0c1dc
Thanks @xortive! - feature: Add support for private networking in Hyperdrive configs#5369
7115568
Thanks @mattdeboard! - fix: Use queue name, not ID, forr2 bucket event-notification
subcommandsSince the original command was not yet operational, this update does not constitute a breaking change.
Instead of providing the queue ID as the parameter to
--queue
, users must provide the queue name. Under the hood, we will query the Queues API for the queue ID given the queue name.#5413
976adec
Thanks @pmiguel! - feature: Added Queue delivery controls support in wrangler.toml#5412
3e5a932
Thanks @RamIdeas! - feature: adds the--json
option towrangler deployments list --experimental-versions
,wrangler deployments status --experimental-versions
,wrangler versions list --experimental-versions
andwrangler versions view --experimental-versions
which will format the output as clean JSON. The--experimental-versions
flag is still required for these commands.#5258
fbdca7d
Thanks @OilyLime! - feature: URL decode components of the Hyperdrive config connection string#5416
47b325a
Thanks @mattdeboard! - fix: minor improvements to R2 notification subcommandr2 bucket event-notification <subcommand>
becomesr2 bucket notification <subcommand>
--event-type
use-
instead of_
(e.g.object_create
->object-create
)Since the original command was not yet operational, this update does not constitute a breaking change.
Patch Changes
#5419
daac6a2
Thanks @RamIdeas! - chore: add helpful logging to --experimental-versions commands#5400
c90dd6b
Thanks @RamIdeas! - chore: log of impending change of "Deployment ID" to "Version ID" inwrangler deploy
,wrangler deployments list
,wrangler deployments view
andwrangler rollback
. This is a warning of a future change for anyone depending on the output text format, for example by grepping the output in automated flows.#5422
b341614
Thanks @geelen! - fix: remove d1BetaWarning and all usagesThis PR removes the warning that D1 is in beta for all D1 commands.
Updated dependencies [
fbdca7d
]:v3.39.0
Compare Source
Minor Changes
#5373
5bd8db8
Thanks @RamIdeas! - feature: Implement versioned rollbacks viawrangler rollback [version-id] --experimental-versions
.Please note, the
experimental-versions
flag is required to use the new behaviour. The originalwrangler rollback
command is unchanged if run without this flag.Patch Changes
#5366
e11e169
Thanks @RamIdeas! - fix: save non-versioned script-settings (logpush, tail_consumers) onwrangler versions deploy
. This command still requires--experimental-versions
.#5405
7c701bf
Thanks @RamIdeas! - chore: addwrangler deployments view [deployment-id] --experimental-versions
commandThis command will display an error message which points the user to run either
wrangler deployments status --experimental-versions
orwrangler versions view <version-id> --experimental-versions
instead.v3.38.0
Compare Source
Minor Changes
#5310
528c011
Thanks @penalosa! - feat: Watch the entire module root for changes in--no-bundle
mode, rather than just the entrypoint file.#5327
7d160c7
Thanks @penalosa! - feat: Addwrangler pages download config
#5284
f5e2367
Thanks @CarmenPopoviciu! - feat: Addwrangler.toml
support inwrangler pages dev
As we are adding
wrangler.toml
support for Pages, we want to ensure thatwrangler pages dev
works with a configuration file.#5353
3be826f
Thanks @penalosa! - feat: Updateswrangler pages functions build
to support using configuration fromwrangler.toml
in the generated output.#5102
ba52208
Thanks @pmiguel! - feature: add support for queue delivery controls onwrangler queues create
Patch Changes
#5327
7d160c7
Thanks @penalosa! - fix: Use specific error code to signal a wrangler.toml file not being found in build-env#5310
528c011
Thanks @penalosa! - fix: Reload Python workers when therequirements.txt
file changesv3.37.0
Compare Source
Minor Changes
#5294
bdc121d
Thanks @mattdeboard! - feature: Addevent-notification
commands in support of event notifications for Cloudflare R2.Included are commands for creating and deleting event notification configurations for individual buckets.
#5231
e88ad44
Thanks @w-kuhn! - feature: Add support for configuring HTTP Pull consumers for QueuesHTTP Pull consumers can be used to pull messages from queues via https request.
Patch Changes
#5317
9fd7eba
Thanks @GregBrimble! - chore: Deprecate-- <command>
,--proxy
and--script-path
options fromwrangler pages dev
.Build your application to a directory and run the
wrangler pages dev <directory>
instead. This results in a more faithful emulation of production behavior.Updated dependencies [
248a318
]:v3.36.0
Compare Source
Minor Changes
#5234
e739b7f
Thanks @CarmenPopoviciu! - feat: Implement environment inheritance for Pages configurationFor Pages, Wrangler will not require both of the supported named environments ("preview" | "production") to be explicitly defined in the config file. If either
[env.production]
or[env.preview]
is left unspecified, Wrangler will use the top-level environment when targeting that named Pages environment.Patch Changes
#5306
c60fed0
Thanks @taylorlee! - fix: Remove triggered_by annotation from experimentalversions deploy
command which is now set by the API and cannot be set by the client.#5321
ac93411
Thanks @RamIdeas! - fix: rename--experimental-gradual-rollouts
to--experimental-versions
flagThe
--experimental-gradual-rollouts
flag has been made an alias and will still work.And additional shorthand alias
--x-versions
has also been added and will work too.#5324
bfc4282
Thanks @penalosa! - fix: Ignore OPTIONS requests in Wrangler's oauth server#5099
93150aa
Thanks @KaiSpencer! - feat: expose--show-interactive-dev-session
flagThis flag controls the interactive mode of the dev session, a feature that already exists internally but was not exposed to the user.
This is useful for CI/CD environments where the interactive mode is not desired, or running in tools like
turbo
andnx
.v3.35.0
Compare Source
Minor Changes
#5166
133a190
Thanks @CarmenPopoviciu! - feat: Implement config file validation for Pages projectsWrangler proper has a mechanism in place through which it validates a wrangler.toml file for Workers projects. As part of adding wrangler toml support for Pages, we need to put a similar mechanism in place, to validate a configuration file against Pages specific requirements.
#5279
0a86050
Thanks @penalosa! - feat: Support the hidden commandwrangler pages functions build-env
#5093
a676f55
Thanks @benycodes! - feature: add --dispatch-namespace to wrangler deploy to support uploading Workers directly to a Workers for Platforms dispatch namespace.Patch Changes
#5275
e1f2576
Thanks @petebacondarwin! - fix: ensure tail exits when the WebSocket disconnectsPreviously when the tail WebSocket disconnected, e.g. because of an Internet failure,
the
wrangler tail
command would just hang and neither exit nor any longer receive tail messages.Now the process exits with an exit code of 1, and outputs an error message.
The error message is formatted appropriately, if the tail format is set to
json
.Fixes #3927
#5069
8f79981
Thanks @RamIdeas! - chore: deprecatewrangler version
commandwrangler version
is an undocumented alias forwrangler --version
. It is being deprecated in favour of the more conventional flag syntax to avoid confusion with a new (upcoming)wrangler versions
command.Updated dependencies [
1720f0a
]:v3.34.2
Compare Source
Patch Changes
a0768bc
Thanks @RamIdeas! - fix:versions upload
annotations (--message
and/or--tag
) are now applied correctly to the uploaded Worker Versionv3.34.1
Compare Source
Patch Changes
2e50d51
]:v3.34.0
Compare Source
Minor Changes
#5224
03484c2
Thanks @RamIdeas! - feature: Implementwrangler deployments list
andwrangler deployments status
behind--experimental-gradual-rollouts
flag.#5115
29e8151
Thanks @RamIdeas! - feature: Implementwrangler versions deploy
command.For now, invocations should use the
--experimental-gradual-rollouts
flag.Without args, a user will be guided through prompts. If args are specified, they are used as the default values for the prompts. If the
--yes
flag is specified, the defaults are automatically accepted for a non-interactive flow.#5208
4730b6c
Thanks @RamIdeas! - feature: Implementwrangler versions list
andwrangler versions view
commands behind the--experimental-gradual-rollouts
flag.#5064
bd935cf
Thanks @OilyLime! - feature: Improve create and update logic for hyperdrive to include caching settingsv3.33.0
Compare Source
Minor Changes
#4930
2680462
Thanks @rozenmd! - refactor: defaultwrangler d1 execute
andwrangler d1 migrations
commands to local mode first, to matchwrangler dev
This PR defaults
wrangler d1 execute
andwrangler d1 migrations
commands to use the local development environment provided by wrangler to match the default behaviour inwrangler dev
.BREAKING CHANGE (for a beta feature):
wrangler d1 execute
andwrangler d1 migrations
commands now default--local
totrue
. When runningwrangler d1 execute
against a remote D1 database, you will need to provide the--remote
flag.Patch Changes
#5184
046930e
Thanks @nora-soderlund! - fix: change d1 migrations create to use the highest migration number rather than the first non-existing migration number to allow for gaps in the migration files.Updated dependencies [
1235d48
,27fb22b
]:v3.32.0
Compare Source
Minor Changes
#5148
11951f3
Thanks @dom96! - chore: bumpworkerd
to1.20240304.0
#5148
11951f3
Thanks @dom96! - fix: use python_workers compat flag for PythonPatch Changes
#5089
5b85dc9
Thanks @DaniFoldi! - fix: include all currently existing bindings inwrangler types
Add support for Email Send, Vectorize, Hyperdrive, mTLS, Browser Rendering and Workers AI bindings in
wrangler types
For example, from the following
wrangler.toml
setup:Previously, nothing would have been included in the generated Environment.
Now, the following will be generated:
Updated dependencies [
11951f3
,11951f3
]:v3.31.0
Compare Source
Minor Changes
#5119
b0bd413
Thanks @garrettgu10! - feature: Python support for remote dev#5118
30694a3
Thanks @garrettgu10! - fix: Including version identifiers in Python requirements.txt will now throw an errorPatch Changes
#5132
82a3f94
Thanks @mrbbot! - fix: switch default logging level ofunstable_dev()
towarn
When running
unstable_dev()
in its default "test mode", the logging level was set tonone
. This meant any Worker startup errors or helpful warnings wouldn't be shown. This change switches the default towarn
. To restore the previous behaviour, includelogLevel: "none"
in your options object:#5128
d27e2a7
Thanks @taylorlee! - fix: Add legacy_env support to experimental versions upload command.#5087
a5231de
Thanks @dario-piotrowicz! - fix: makewrangler types
always generate ad.ts
file for module workersCurrently if a config file doesn't define any binding nor module, running
wrangler types
against such file would not produce ad.ts
file.Producing a
d.ts
file can however still be beneficial as it would define a correctenv interface (even if empty) that can be expanded/referenced by user code (this can
be particularly convenient for scaffolding tools that may want to always generate an
env interface).
Example:
Before
wrangler types --env-interface MyEnv
run with an emptywrangler.toml
filewould not generate any file, after these change it would instead generate a file with
the following content:
#5138
3dd9089
Thanks @G4brym! - fix: ensure Workers-AI local mode fetcher returns headers to client workerUpdated dependencies [
42bcc72
,42bcc72
]:v3.30.1
Compare Source
Patch Changes
#5106
2ed7f32
Thanks @RamIdeas! - fix: automatically drain incoming request bodiesPreviously, requests sent to
wrangler dev
with unconsumed bodies could result inNetwork connection lost
errors. This change attempts to work around the issue by ensuring incoming request bodies are drained if they're not used. This is a temporary fix whilst we try to address the underlying issue. Whilst we don't think this change will introduce any other issues, it can be disabled by setting theWRANGLER_DISABLE_REQUEST_BODY_DRAINING=true
environment variable. Note this fix is only applied if you've enabled Wrangler's bundling—--no-bundle
mode continues to have the previous behaviour.#5107
65d0399
Thanks @penalosa! - fix: Ensures that switching to remote mode during a dev session (from local mode) will correctly use the right zone. Previously, zone detection happened before the dev session was mounted, and so dev sessions started with local mode would have no zone inferred, and would have failed to start, with an ugly error.#5107
65d0399
Thanks @penalosa! - fix: Ensure that preview sessions created without a zone don't switch the host on which to start the preview from the one returned by the API.#4833
54f6bfc
Thanks @admah! - fix: remove extra arguments from wrangler init deprecation message and update recommended c3 versionc3 can now infer the pre-existing type from the presence of the
--existing-script
flag so we can remove the extratype
argument. C3 2.5.0 introduces an auto-update feature that will make sure users get the latest minor version of c3 and prevent problems where older 2.x.x versions get cached by previous runs ofwrangler init
.v3.30.0
Compare Source
Minor Changes
#4742
c2f3f1e
Thanks @benycodes! - feat: allow preserving file names when defining rules for non-js modulesThe developer is now able to specify the `preserve_file_names property in wrangler.toml
which specifies whether Wrangler will preserve the file names additional modules that are
added to the deployment bundle of a Worker.
If not set to true, files will be named using the pattern ${fileHash}-${basename}.
For example,
34de60b44167af5c5a709e62a4e20c4f18c9e3b6-favicon.ico
.Resolves #4741
Patch Changes
0c0949d
]:v3.29.0
Compare Source
Minor Changes
#5042
5693d076
Thanks @dario-piotrowicz! - feat: add new--env-interface
towrangler types
Allow users to specify the name of the interface that they want
wrangler types
to generate for theenv
parameter, via the new CLI flag--env-interface
Example:
generates
instead of
#5042
5693d076
Thanks @dario-piotrowicz! - feat: add newpath
positional argument towrangler types
Allow users to specify the path to the typings (.d.ts) file they want
wrangler types
to generateExample:
generates a
my-env.d.ts
file in the current directoryinstead of creating a
worker-configuration.d.ts
filePatch Changes
#5042
5693d076
Thanks @dario-piotrowicz! - feat: include command run in thewrangler types
commentIn the comment added to the
.d.ts
file generated bywrangler types
include the command run to generated the file
1c460287
Thanks @richardscarrott! - fix: allow Pages Functions to import built-in node:* modules, even when not bundling with wrangler50f93bd2
Thanks @garrettgu10! - fix: don't strip.py
extensions from Python modules#5042
5693d076
Thanks @dario-piotrowicz! - fix: makewrangler types
honor top level config argumentThe
wrangler types
command currently ignores the-c|--config
argument(although it is still getting shown in the command's help message). Make
sure that the command honors the flag.
Also, if no config file is detected
present a warning to the user
#5042
5693d076
Thanks @dario-piotrowicz! - fix: make thewrangler types
command pick up local secret keys from.dev.vars
Make sure that the
wrangler types
command correctly picks upsecret keys defined in
.dev.vars
and includes them in the generatedfile (marking them as generic
string
types of course)Updated dependencies [
b03db864
]:v3.28.4
Compare Source
Patch Changes
#5050
88be4b84
Thanks @nora-soderlund! - fix: allow kv:namespace create to accept a namespace name that contains characters not allowed in a binding nameThis command tries to use the namespace name as the binding. Previously, we would unnecessarily error if this namespace name did not fit the binding name constraints. Now we accept such names and then remove invalid characters when generating the binding name.
v3.28.3
Compare Source
Patch Changes
#5026
04584722
Thanks @dario-piotrowicz! - fix: make suregetPlatformProxy
produces a production-likecaches
objectmake sure that the
caches
object returned togetPlatformProxy
behavesin the same manner as the one present in production (where calling unsupported
methods throws a helpful error message)
note: make sure that the unsupported methods are however not included in the
CacheStorage
type definition#5030
55ea0721
Thanks @mrbbot! - fix: don't suggest reporting user errors to GitHubWrangler has two different types of errors: internal errors caused by something going wrong, and user errors caused by an invalid configuration. Previously, we would encourage users to submit bug reports for user errors, even though there's nothing we can do to fix them. This change ensures we only suggest this for internal errors.
#4900
3389f2e9
Thanks @OilyLime! - feature: allow hyperdrive users to set local connection string as environment variableWrangler dev now supports the HYPERDRIVE_LOCAL_CONNECTION_STRING environmental variable for connecting to a local database instance when testing Hyperdrive in local development. This environmental variable takes precedence over the localConnectionString set in wrangler.toml.
#5033
b1ace91b
Thanks @mrbbot! - fix: wait for actual port before opening browser with--port=0
Previously, running
wrangler dev --remote --port=0
and then immediately pressingb
would openlocalhost:0
in your default browser. This change queues up opening the browser until Wrangler knows the port the dev server was started on.#5026
04584722
Thanks @dario-piotrowicz! - fix: relax thegetPlatformProxy
's' cache request/response typesprior to these changes the caches obtained from
getPlatformProxy
would use
unknown
s as their types, this proved too restrictiveand incompatible with the equivalent
@cloudflare/workers-types
types, we decided to use
any
s instead to allow for more flexibilitywhilst also making the type compatible with workers-types
Updated dependencies [
7723ac17
,027f9719
,027f9719
,027f9719
,027f9719
,027f9719
,027f9719
]:v3.28.2
Compare Source
Patch Changes
#4950
05360e43
Thanks @petebacondarwin! - fix: ensure we do not rewrite external Origin headers in wrangler devIn https://github.com/cloudflare/workers-sdk/pull/4812 we tried to fix the Origin headers to match the Host header but were overzealous and rewrote Origin headers for external origins (outside of the proxy server's origin).
This is now fixed, and moreover we rewrite any headers that refer to the proxy server on the request with the configured host and vice versa on the response.
This should ensure that CORS is not broken in browsers when a different host is being simulated based on routes in the Wrangler configuration.
bfeefe27
Thanks @dario-piotrowicz! - chore: add missingdefineNavigatorUserAgent
dependency to useEsbuild hook36692326
Thanks @penalosa! - fix: Report Custom Build failures asUserError
s#5002
315a651b
Thanks @dario-piotrowicz! - chore: renamegetBindingsProxy
togetPlatformProxy
initially
getBindingsProxy
was supposed to only provide proxies for bindings,the utility has however grown, including now
cf
,ctx
andcaches
, toclarify the increased scope the utility is getting renamed to
getPlatformProxy
and its
bindings
field is getting renamedenv
note:
getBindingProxy
with its signature is still kept available, making thisa non breaking change
Updated dependencies [
05360e43
]:v3.28.1
Compare Source
Patch Changes
#4962
d6585178
Thanks @mrbbot! - fix: ensurewrangler dev
can reload without crashing when importingnode:*
modulesThe previous Wrangler release introduced a regression that caused reloads to fail when importing
node:*
modules. This change fixes that, and ensures these modules can always be resolved.ffafe8ad
Thanks @nora-soderlund! - fix: D1 batch splitting to handle CASE as compound statement startsv3.28.0
Compare Source
Minor Changes
#4499
cf9c029b
Thanks @penalosa! - feat: Support runtime-agnostic polyfillsPreviously, Wrangler treated any imports of
node:*
modules as build-time errors (unless one of the two Node.js compatibility modes was enabled). This is sometimes overly aggressive, since those imports are often not hit at runtime (for instance, it was impossible to write a library that worked across Node.JS and Workers, using Node packages only when running in Node). Here's an example of a function that would cause Wrangler to fail to build: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.
This PR has been generated by Mend Renovate. View repository job log here.