chore(deps): update all non-major dependencies #1959
Merged
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}
✅
|
✅
|
✅
|
✅
|
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@whatwg-node/fetch |
0.10.2-alpha-20250109232708-2991d90eb21112e812c9058f8263208dd56c7280 |
npm ↗︎ unpkg ↗︎ |
@whatwg-node/node-fetch |
0.7.6-alpha-20250109232708-2991d90eb21112e812c9058f8263208dd56c7280 |
npm ↗︎ unpkg ↗︎ |
✅
|
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:
2.1.4->2.1.53.100.0->3.101.0Release Notes
denoland/deno (deno)
v2.1.5Compare Source
directories (#27395)
(#27429)
unavailable (#27463)
Deno.resolveDnson some laptops with Ryzen CPU (#27572)
fs.access/fs.promises.accesswithX_OKmode parameteron Windows (#27407)
os.cpus()on Linux (#27592)truncatemethod to theFileHandleclass (#27389)(#27476)
(#27378)
processglobal available in Node context (#27562)[[ErrorData]]slot toDOMException(#27342)(#27337)
inspector/promises(#27491)(#27345)
(#27390)
--allow-importwhen using--cached-only(#27530)
(#27437)
cloudflare/workers-sdk (wrangler)
v3.101.0Compare Source
Minor Changes
#7534
7c8ae1cThanks @cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines#7674
45d1d1eThanks @Ankcorn! - Add support for env files to wrangler secret bulk i.e..dev.varsRun
wrangler secret bulk .dev.varsto add the env fileThis will upload the secrets KEY and KEY_2 to your worker
#7442
e4716ccThanks @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 deploywrangler devwrangler versions uploadwrangler versions deploywrangler pages deploywrangler pages buildwrangler pages build-envConfig 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.jsonfile) 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.tomlfile.Note that this configuration points
mainat user code entry-point.The user runs a custom build, which might read the
wrangler.tomlto find the entry-point:> my-tool buildThis tool generates a
distdirectory that contains both compiled code and a new deployment configuration file, but also a.wrangler/deploy/config.jsonfile that redirects Wrangler to this new deployment configuration file:The
dist/wrangler.jsonwill contain:{ "name": "my-worker", "main": "./index.js", "kv_namespaces": [ { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" } ] }And the
.wrangler/deploy/config.jsonwill contain:{ "configPath": "../../dist/wrangler.json" }#7685
9d2740aThanks @vicb! - 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.
#7694
f3c2f69Thanks @joshthoward! - Default wrangler d1 export to --local rather than failingPatch Changes
#7456
ff4e77eThanks @andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.#7712
6439347Thanks @penalosa! - Remove CF-Connecting-IP for requests to the edge preview#7703
e771fe9Thanks @petebacondarwin! - include the top level Worker name in the parsed config structure#7576
773bda8Thanks @cmackenzie1! - Remove defaults forbatch-max-*pipeline parameters and define value rangesUpdated dependencies [
2c76887,78bdec5]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.