-
-
Notifications
You must be signed in to change notification settings - Fork 38
chore(deps): update dependency wrangler to v4 #108
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
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/wrangler-4.x
base: master
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 hidden or 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
Deploying auth-wiki with
|
| Latest commit: |
7ae565f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d5662a2c.auth-wiki.pages.dev |
| Branch Preview URL: | https://renovate-wrangler-4-x.auth-wiki.pages.dev |
849cd87 to
328b580
Compare
328b580 to
0b8de61
Compare
0b8de61 to
4a53e8d
Compare
4a53e8d to
8db9180
Compare
8db9180 to
38e2537
Compare
38e2537 to
7915a1a
Compare
7915a1a to
f755880
Compare
f755880 to
8ba1ff2
Compare
8ba1ff2 to
ae902e1
Compare
ae902e1 to
8da841b
Compare
8da841b to
fe8927b
Compare
fe8927b to
67f81aa
Compare
67f81aa to
7b65a43
Compare
7b65a43 to
cd1a021
Compare
6ed9db4 to
1693fee
Compare
1693fee to
033a7cf
Compare
033a7cf to
f9f2299
Compare
f9f2299 to
3b50962
Compare
d1e1dae to
3d7c016
Compare
3d7c016 to
1dc23b6
Compare
1dc23b6 to
04b314e
Compare
04b314e to
ad1029a
Compare
ad1029a to
f3b22f6
Compare
f3b22f6 to
07828eb
Compare
07828eb to
b8416f0
Compare
b8416f0 to
ddc46b5
Compare
ddc46b5 to
7ae565f
Compare
7ae565f to
b7fa8d2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^3.99.0->^4.0.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.53.0Compare Source
Minor Changes
#11500
af54c63Thanks @dario-piotrowicz! - Add newautoconfig_summaryfield to the deploy output entryThis change augments
wrangler deployoutput being printed toWRANGLER_OUTPUT_FILE_DIRECTORYorWRANGLER_OUTPUT_FILE_PATHto also include a newautoconfig_summaryfield containing the possible summary details for the autoconfig process (the field isundefinedif autoconfig didn't run).Note: the field is experimental and could change while autoconfig is not GA
#11477
9988cc9Thanks @ascorbic! - Support Nuxt in autoconfig#11472
ce295bfThanks @dario-piotrowicz! - Support Qwik projects in autoconfig#10937
9514c9aThanks @ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fieldsThis change adds a new mode to
placementconfiguration. You can specify one of the following fields to target specific external resources for Worker placement:region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service providerhost: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP servicehostname: Specify a hostname (e.g., "example.com") to target an HTTP resourceThese fields are mutually exclusive - only one can be specified at a time.
Example configuration:
#11498
ac861f8Thanks @penalosa! - Add React Router support in autoconfig#11506
79d30d4Thanks @vicb! - Set the target JS version to ES2024Patch Changes
#11393
45480b1Thanks @alsuren! - improved --help text for wrangler d1 subcommands#11523
94c67e8Thanks @jamesopstad! - fix: types from @cloudflare/workers-utils not being exported correctly from Wrangler#11483
f550b62Thanks @edmundhung! - stop runningnpm installwith--legacy-peer-depsflag when setting up a projectUpdated dependencies [
819e287,56e78c8,0aa959a]:v4.52.1Compare Source
Patch Changes
#11504
7e80340Thanks @dario-piotrowicz! - Fixwrangler deployfailing for new workers containing environment variables or bindingsUpdated dependencies [
59534ba]:v4.52.0Compare Source
Minor Changes
#11416
abe49d8Thanks @dario-piotrowicz! - Remove thewrangler deploy's--x-remote-diff-checkexperimental flagThe remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.
#11408
f29e699Thanks @ascorbic! - Export unstable helpers useful for generating wrangler config#11389
2342d2fThanks @dario-piotrowicz! - Improve thewrangler deployflow to also check for potential overrides of secrets.Now when you run
wrangler deployWrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.#11375
9a1de61Thanks @penalosa! - Support TanStack Start in autoconfig#11360
6b38532Thanks @emily-shen! - Containers: Allow users to directly authenticate external image registries in local devPreviously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.
Now you can directly authenticate with your external registry provider (using
docker loginetc.), and Wrangler or Vite will be able to pull the image specified in thecontainers.imagefield in your config file.The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.
#11009
e4ddbc2Thanks @dario-piotrowicz! - Allow users to provide anaccount_idas part of theWorkerConfigObjectthey pass tomaybeStartOrUpdateRemoteProxySession#11478
2aec2b4Thanks @dario-piotrowicz! - Support SolidStart in autoconfig#11330
5a873bbThanks @dario-piotrowicz! - Support Angular projects in autoconfig#11449
e7b690bThanks @penalosa! - Delegate generation of HTTPS certificates to Miniflare#11448
2b4813bThanks @edmundhung! - Bumpsesbuildversion to 0.27.0#11335
c47ad11Thanks @dario-piotrowicz! - Support internal-only undocumentedcross_account_grantservice binding property#11346
a977701Thanks @penalosa! - We're soon going to make backend changes that mean thatwrangler dev --remotesessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a newwrangler tail-based logging strategy forwrangler dev --remote. For now, you can revert to the previous logging strategy withwrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.
Patch Changes
#11397
b154de2Thanks @vicb! - Use more workerd native modulesNode modules
punycode,trace_events,cluster,wasi, anddomainswill be used when enabledvia a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.
#11452
76f0540Thanks @penalosa! - Remove uses ofeval()from the Wrangler bundle#11284
695fa25Thanks @dom96! - Removes duplicate module warnings when vendoring Python packages#11249
504e258Thanks @dario-piotrowicz! - fix: Generalize autoconfig wordingGeneralize the autoconfig wording so that when it doesn't specifically mention "deployment" (since it can be run via
wrangler setupor the autoconfig programmatic API)#11455
d25f7e2Thanks @dario-piotrowicz! - Fix autoconfig using absolute paths for static projectsRunning the experimental autoconfig logic through
wrangler setupandwrangler deploy --x-autoconfigon a static project results in absolute paths being used. This is incorrect, especially when such paths are being included in the generated wrangler.jsonc. The changes here fix the autoconfig logic to use paths relative to the project's root instead.For example given a project located in
/Users/usr/projects/sites/my-static-site, before:and after:
#11484
1cfae2dThanks @edmundhung! - Explicitly close FileHandle inwrangler d1 executeto support Node 25#11383
1d685cbThanks @dario-piotrowicz! - Fix: ensure that when a remote proxy session creation fails a hard error is surfaced to the user (both inwrangler devand in the programmatic API).When using remote bindings, either with
wrangler devor viastartRemoteProxySession/maybeStartOrUpdateRemoteProxySessionthe remote proxy session necessary to connect to the remote resources can fail to be created, this might happen if for example you try to set a binding with some invalid values such as:Before this could go undetected and cause unwanted behaviors such as requests handling hanging indefinitely, now wrangler will instead crash (or throw a hard error ion the programmatic API), clearly indicating that something went wrong during the remote session's creation.
#11366
edf896dThanks @ascorbic! - Use correctly-formatted names when displaying detected framework details#11461
9eaa9e2Thanks @dario-piotrowicz! - Update the structure of theconfiguremethod of autoconfig frameworksUpdate the signature of the
configurefunction of autoconfig frameworks (AutoconfigDetails#Framework), before they would return aRawConfigobject to use to update the project's wrangler config file, now they return an object that includes theRawConfigand that can potentially also hold additional data relevant to the configuration.Updated dependencies [
2b4813b,b154de2,5ee3780,6e63b57,71ab562,5e937c1]:v4.51.0Compare Source
Minor Changes
#11345
d524e55Thanks @penalosa! - Enable experimental support for autoconfig-powered Astro projects#11228
43903a3Thanks @petebacondarwin! - SupportCLOUDFLARE_ENVenvironment variable for selecting the active environmentThis change enables users to select the environment for commands such as
CLOUDFLARE_ENV=prod wrangler versions upload. The--envcommand line argument takes precedence.The
CLOUDFLARE_ENVenvironment variable is mostly used with the@cloudflare/vite-pluginto select the environment for building the Worker to be deployed. This build also generates a "redirected deploy config" that is flattened to only contain the active environment.To avoid accidentally deploying a version that is built for one environment to a different environment, there is an additional check to ensure that if the user specifies an environment in Wrangler it matches the original selected environment from the build.
Patch Changes
#11367
e496280Thanks @vicb! - Rate limit r2 bulk putUpdated dependencies [
4d61fae,69f4dc3,1133c4d,4d61fae]:v4.50.0Compare Source
Minor Changes
#11219
524a6e5Thanks @Ltadrian! - Implement Hyperdrive binding TLS miniflare proxy. This will allow for wrangler dev hyperdrive bindings to connect to externaldatabases that require TLS.
#11233
c922a81Thanks @emily-shen! - Addcontainers.unsafeto allow internal users to use additional container featuresPatch Changes
#11353
0cf696dThanks @vicb! - Use the nativenode:domainmodule when availableIt is enabled when the
enable_nodejs_domain_modulecompatibility flag is set.#11328
bb44120Thanks @ascorbic! - Fixes a bug that causedwrangler deployto hang when deploying SvelteKit sites with experimental autoconfig#11025
4a158e9Thanks @devin-ai-integration! - Use the nativenode:wasimodule when availableIt is enabled when the
enable_nodejs_wasi_modulecompatibility flag is set.Updated dependencies [
0cf696d,524a6e5,4a158e9]:v4.49.1Compare Source
Patch Changes
#11344
c758809Thanks @dario-piotrowicz! - Fix: mark ther2 bulkcommand as hidden and experimental#11339
dfba912Thanks @dario-piotrowicz! - Fixwrangler deployerroring when it pulls down remote configs of workers containing an assets bindingUpdated dependencies [
e5ec8cf]:v4.49.0Compare Source
Minor Changes
#10703
c5c4ee5Thanks @danlapid! - Add support for streaming tail consumers in local dev. This is an experimental new feature that allows you to register atailStream()handler (compared to the existingtail()handler), which will receive streamed tail events from your Worker (compared to thetail()handler, which only receives batched events after your Worker has finished processing).#11251
7035804Thanks @penalosa! - When theWRANGLER_HIDE_BANNERenvironment variable is provided, Wrangler will no longer display a version banner. This applies to all commands.For instance, previously running
wrangler docswould give the following output:With
WRANGLER_HIDE_BANNER, this is now:#11285
d014fa7Thanks @vicb! - Implement thewrangler r2 bulk put bucket-name --filename list.jsoncommand.The command uploads multiple objects to an R2 bucket.
The list of object is provided as a JSON encoded file via
--filename. It is a list of key and file (respectively the name and the content for the object).Uploads are executed concurrently and the level of concurrency can be set via
--concurrency.The command supports the same options as
wrangler r2 object put, minus--file, and--pipeand plus--concurrency#11268
15b8460Thanks @penalosa! - Support SvelteKit projects in autoconfig#11258
2011b6aThanks @dario-piotrowicz! - Add--dry-runflag towrangler setupand also adryRunoption torunAutoConfigPatch Changes
#11261
a352c7fThanks @petebacondarwin! - Avoid using object lookup for OAuth Error classes#11286
8e99766Thanks @dario-piotrowicz! - fix: make sure thatexperimental_patchConfigdoesn't throw if it encounters anullvalue#11279
d0d3fe6Thanks @vicb! - bump p-queue to ^9.0.0#11278
92afbbaThanks @ascorbic! - Fixes a bug that caused.dev.varsto be ignored in OpenNext#11244
65b4afeThanks @petebacondarwin! - Internal refactoring to improve error traceability in wrangler dev#11238
da8442fThanks @jamesopstad! - Addunstable_getDurableObjectClassNameToUseSQLiteMapexport. This is an internal function for use in the Vite plugin.#11266
09cb720Thanks @penalosa! - Use the smol-toml library for parsing TOML instead of @iarna/toml#11236
793e2b4Thanks @ascorbic! - Refresh expired preview tokens when running in remote dev mode#11286
8e99766Thanks @dario-piotrowicz! - fix:wrangler deployfailing to patch localwrangler.jsoncfiles if the remotetail_consumersvalue isnull#11275
9cbf126Thanks @dario-piotrowicz! - Ensure thatwrangler deployrun with a positional argument or with--assetsdoes not trigger the autoconfig process (even with--experimental-autoconfig)#11242
dd1e560Thanks @dario-piotrowicz! - Fix: make sure that remote proxy sessions's debug logs are enabled when the wrangler log level is set to "debug"Updated dependencies [
c5c4ee5,d0041e2,827d017]:v4.48.0Compare Source
Minor Changes
#11212
3908162Thanks @dario-piotrowicz! - Add autoconfig changes summary forwrangler deploy --x-autoconfigwith the option for users to cancel the operation#11229
14d79f2Thanks @dario-piotrowicz! - Enablesexperimental-deploy-remote-diff-checkflag by default (the flag is still present for now so that users can turn it off if needed) and improves the remote config diffing logic (to include less noise in the diff presented to the user)#11245
dfc6513Thanks @vicb! - Change how Wrangler selects default ports for dev sessions.If no port is specified, Wrangler now probes the default port and the 10 consecutive ports after it before falling back to a random port.
This will help getting a stable port number across dev sessions.
Both the http server and inspector ports are affected.
Patch Changes
#11177
43fe9f3Thanks @MattieTK! - Added bun detection to package manager analyticsUpdated dependencies [
305ffb3,46ccf0e]:v4.47.0Compare Source
Minor Changes
#11201
5286309Thanks @avenceslau! - Add wrangler workflows instances restart command#11214
5cf8a39Thanks @penalosa! - Add the experimentalwrangler setupcommand to run autoconfig outside of the deploy flow.#11187
8abc789Thanks @dario-piotrowicz! - Add possibility for users to edit their project settings during autoconfigWhen running
wrangler deploy --experimental-autoconfig, after the automatic project settings detection Wrangler will now present users the opportunity to customize the auto-detected project's settingsPatch Changes
#11143
2d16610Thanks @FlorentCollin! - Improve the formatting of the D1 execute command to always show the duration in milliseconds with two decimal places.#11178
63defa2Thanks @ascorbic! - Log a more helpful error when attempting to "r2 object put" a non-existent file#11199
70d3d4aThanks @penalosa! - Add telemetry to autoconfig#11186
38396edThanks @hoodmane! - Removed warning when deploying a Python worker#11024
cdcecfcThanks @devin-ai-integration! - Use the nativenode:trace_eventsmodule when availableIt is enabled when the
enable_nodejs_trace_events_modulecompatibility flag is set.#11195
e85f965Thanks @ascorbic! - Ignores.dev.varsif--env-filehas been explicitly passedPreviously,
.dev.varswould always be read first, and then any file passed with--env-filewould override variables in.dev.vars. This meant there was no way to ignore.dev.varsif you wanted to use a different env file. Now, if--env-fileis passed,.dev.varswill be ignored entirely.#11181
88aa707Thanks @petebacondarwin! - add more logging around Wrangler authentication to help diagnose issuesUpdated dependencies [
dd7d584,4259256,cdcecfc]:v4.46.0Compare Source
Minor Changes
#11183
240ebebThanks @dario-piotrowicz! - exposeexperimental_getDetailsForAutoConfigandexperimental_runAutoConfigAPIs that provide respectively the autoconfig detection and execution functionalities#11180
53b0fceThanks @penalosa! - Detect non-framework static sites#11162
c3ed531Thanks @dario-piotrowicz! - add aremoteBindingsoption togetPlatformProxyto allow the disabling of remote bindings#11164
305d7bfThanks @penalosa! - Implement experimental autoconfig flow for static sites#10605
b55a3c7Thanks @emily-shen! - Add command to configure credentials for non-Cloudflare container registriesNote this is a closed/experimental command that will not work without the appropriate account-level capabilities.
#11078
5d7c4c2Thanks @simonha9! - Add jurisdiction support to d1 db creation via command-line argumentPatch Changes
#11160
05440a1Thanks @dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when runningwrangler deploy --env <TARGET_ENV>When running
wrangler deploy, with--x-remote-diff-checkand after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the--env|-eflag). Now this will also apply when an environment is targeted.#11162
c3ed531Thanks @dario-piotrowicz! - Update the description of the--localflag for thewrangler devcommand to clarify that it disables remote bindings, also un-deprecate and un-hide it#11162
c3ed531Thanks @dario-piotrowicz! - Fix bindings withremote: truebeing logged asremotewhen run viawrangler dev --localUpdated dependencies [
1ae020d]:v4.45.4Compare Source
Patch Changes
#11133
8ffbd17Thanks @petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.Now the argument values that are captured come from an allow list,
and can be marked as ALLOW (capture the real value) or REDACT (capture as "").
#11033
77ed7e2Thanks @dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when runningwrangler deployWhen running
wrangler deploy, with--x-remote-diff-check, Wrangler will display the difference between local and remote configuration.If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment.
In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.
#11139
bb00f9dThanks @devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally#11135
ed666a1Thanks @penalosa! - Implement tail-based logging forwrangler devremote mode, behind the--x-tail-tagsflag. This will become the default in the future.#11149
22f25fdThanks @penalosa! - Add no-op autoconfig logic behind an experimental flagUpdated dependencies [
90a2566,14f60e8]:v4.45.3Patch Changes
#11117
6822aafThanks @emily-shen! - fix: show local/remote status before D1 command confirmationsD1 commands (
execute,export,migrations apply,migrations list,delete,time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.#11077
bce8142Thanks @petebacondarwin! - Ensure that process.env is case-insensitive on WindowsThe object that holds the environment variables in
process.envdoes not care about the case of its keysin Windows. For example,
process.env.SystemRootandprocess.env.SYSTEMROOTwill refer to the same value.Previously, when merging fields from
.envfiles we were replacing this native object with a vanillaJavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
when in reality they just had different casing.
v4.45.2Patch Changes
#11097
55657ebThanks @penalosa! - Extract internal APIs into a new@cloudflare/workers-utilspackage#11118
d47f166Thanks @zebp! - Fix validation of thepersistfield of observabilitylogsandtracesconfigurationv4.45.1Compare Source
Patch Changes
#10959
d0208feThanks @devin-ai-integration! - Fixed conflict between--envand--expiresflags inwrangler r2 object put.--enow aliases--envonly, and NOT--expires.#10915
dbe51c1Thanks @devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.#10913
d4f2dafThanks @devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occurv4.45.0Compare Source
Minor Changes
#11030
1a8088aThanks @penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the--no-x-provisionflag. It currently works for R2, D1, and KV bindings.To use this feature, add a binding to your config file without a resource ID:
{ "kv_namespaces": [{ "binding": "MY_KV" }], "d1_databases": [{ "binding": "MY_DB" }], "r2_buckets": [{ "binding": "MY_R2" }], }wrangler devwill automatically create these resources for you locally, and when you next runwrangler deployWrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.Patch Changes
#11037
4bd4c29Thanks @danielrs! - Better Wrangler subdomain defaults warning.Improves the warnings that we show users when either
worker_devorpreview_urlsare missing.#10927
31e1330Thanks @dom96! - Implementspython_modules.excludeswrangler config field#10741
2f57345Thanks @penalosa! - Remove obsolete--x-remote-bindingsflagUpdated dependencies [
ca6c010]:v4.44.0Compare Source
Minor Changes
#10939
d4b4c90Thanks @danielrs! - Configpreview_urlsdefaults toworkers_devvalue.Originally, we were defaulting config.preview_urls to
true, but wewere accidentally enabling Preview URLs for users that only had
config.workers_dev=false.
Then, we set the default value of config.preview_urls to
false, but wewere accidentally disabling Preview URLs for users that only had
config.workers_dev=true.
Rather than defaulting config.preview_urls to
trueorfalse, wedefault to the resolved value of config.workers_dev. Should result in a
clearer user experience.
#11027
1a2bbf8Thanks @jamesopstad! - Statically replace the value ofprocess.env.NODE_ENVwithdevelopmentfor development builds andproductionfor production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based onprocess.env.NODE_ENVcan be properly tree shaken.#9705
0ee1a68Thanks @hiendv! - Add params type to Workflow type generation. E.g.#10867
dd5f769Thanks @austin-mc! - Add media binding supportPatch Changes
#11018
5124818Thanks @dario-piotrowicz! - Improve potential errors thrown bystartRemoteProxySessionby including more information#11019 [
6643bd4](https://redirect.github.com/cloudflare/workers-sdk/commit/6643bd41a082f04778739b93a872Configuration
📅 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 was generated by Mend Renovate. View the repository job log.