fix(deps): update core #71
Open
+398
−413
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
zackpollard
approved these changes
Dec 17, 2024
renovate
bot
force-pushed
the
renovate/core
branch
4 times, most recently
from
082cf0a to
9112d36
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core
branch
from
9112d36 to
646c9b6
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/core
branch
13 times, most recently
from
a21da3c to
7555d6b
Compare
renovate
bot
force-pushed
the
renovate/core
branch
from
7555d6b to
0a8d45c
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.709.0->3.717.00.5.36->0.5.404.20241205.0->4.20241218.04.20241224.08.18.0->8.18.18.18.28.18.0->8.18.18.18.24.48.0->4.49.16.1.0->6.2.03.95.0->3.99.0Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-s3)
v3.717.0Compare Source
Note: Version bump only for package @aws-sdk/client-s3
v3.716.0Compare Source
Note: Version bump only for package @aws-sdk/client-s3
v3.715.0Compare Source
Note: Version bump only for package @aws-sdk/client-s3
v3.714.0Compare Source
Features
v3.713.0Compare Source
Note: Version bump only for package @aws-sdk/client-s3
v3.712.0Compare Source
Note: Version bump only for package @aws-sdk/client-s3
cloudflare/workers-sdk (@cloudflare/vitest-pool-workers)
v0.5.40Compare Source
Patch Changes
1488e11,7216835,48e7e10,8757579,086a6b8,2bbcb93]:v0.5.39Compare Source
Patch Changes
fb819f9,5124b5d,42b9429,72935f9,8def8c9]:v0.5.38Compare Source
Patch Changes
ca9410a,6403e41,15aa936,2780849]:v0.5.37Compare Source
Patch Changes
004af53,f13c897,8af3365,0356d0a,2e90efc,11f95f7,3bc0f28]:cloudflare/workerd (@cloudflare/workers-types)
v4.20241218.0Compare Source
v4.20241216.0Compare Source
v4.20241214.0Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.18.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.18.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
cloudflare/terraform-provider-cloudflare (cloudflare)
v4.49.1Compare Source
Functionally the same as v4.49.0 but retagged to fix the Terraform Registry having a bad checksum due to a failed build asset being used.
v4.49.0Compare Source
NOTES:
policy_idsattribute (#4817)FEATURES:
cloudflare_content_scanning_expression(#4734)cloudflare_content_scanning(#4719)ENHANCEMENTS:
BUG FIXES:
disable_stale_while_updatingis an empty object but not nil (#4814)DEPENDENCIES:
sindresorhus/p-limit (p-limit)
v6.2.0Compare Source
limitFunction()(#88)ef48184cloudflare/workers-sdk (wrangler)
v3.99.0Compare Source
Minor Changes
#7425
8757579Thanks @CarmenPopoviciu! - feat: Make DX improvements inwrangler dev --remoteWorkers + Assets projects have, in certain situations, a relatively degraded
wrangler dev --remotedeveloper experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:This commit improves the
wrangler dev --remoteDX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.#7537
086a6b8Thanks @WillTaylorDev! - Provide validation around assets.experimental_serve_directly#7568
2bbcb93Thanks @WillTaylorDev! - Warn users when using smart placement with Workers + Assets andserve_directlyis set tofalsePatch Changes
#7521
48e7e10Thanks @emily-shen! - feat: add experimental_patchConfig()experimental_patchConfig()can add to a user's config file. It preserves comments if its awrangler.jsonc. However, it is not suitable forwrangler.tomlwith comments as we cannot preserve comments on write.Updated dependencies [
1488e11,7216835]:v3.98.0Compare Source
Minor Changes
#7476
5124b5dThanks @WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example,example.com/blog/*can now be used to serve assets.These assets will be served as though the assets directly were mounted to the root.
For example, if you have
assets = { directory = "./public/" }, a route like"example.com/blog/*"and a file./public/blog/logo.png, this will be available atexample.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.#7380
72935f9Thanks @CarmenPopoviciu! - Add Workers + Assets support inwrangler dev --remotePatch Changes
#7573
fb819f9Thanks @emily-shen! - feat: add experimental_readRawConfig()Adds a Wrangler API to find and read a config file
#7549
42b9429Thanks @penalosa! - Expand metrics collection to:--x-versions,--x-dev-env, and--latest) by only including args that were inargv#7583
8def8c9Thanks @penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects withnodejs_compat_v2in some casesv3.97.0Compare Source
Minor Changes
#7522
6403e41Thanks @vicb! - feat(wrangler): allow overriding the unenv preset.By default wrangler uses the bundled unenv preset.
Setting
WRANGLER_UNENV_RESOLVE_PATHSallow 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.
#7479
2780849Thanks @penalosa! - Accept a JSON file of the format{ name: string }[]inwrangler kv bulk delete, as well as the currentstring[]format.Patch Changes
#7541
ca9410aThanks @vicb! - chore(wrangler): update unenv dependency version#7345
15aa936Thanks @edmundhung! - fix(wrangler): keypress event name is optionalv3.96.0Compare Source
Minor Changes
#7510
004af53Thanks @oliy! - Add file prefix option to wrangler pipelines commands#7383
8af3365Thanks @jonesphillip! - Added wrangler r2 domain get commandPatch Changes
#7542
f13c897Thanks @CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commandsCurrently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.
#6754
0356d0aThanks @bluwy! - refactor: move@cloudflare/workers-sharedas dev dependency#7478
2e90efcThanks @petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environmentIt is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration.
But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment.
Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration.
Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.
#7524
11f95f7Thanks @gpanders! - Include response body in Cloudchamber API errors#7427
3bc0f28Thanks @edmundhung! - Thex-provisionexperimental flag now identifies draft and inherit bindings by looking up the current binding settings.Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during
wrangler deploy.Updated dependencies []:
Configuration
📅 Schedule: Branch creation - "on tuesday" (UTC), 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.