fix(deps): upgrade npm packages by renovate[bot] · Pull Request #19 · Pycord-Development/pycord-crowdin-linked-roles

renovate · 2025-10-22T04:57:39Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/workers-types	`4.20251014.0` → `4.20260501.1`
hono (source)	`4.12.14` → `4.12.16`
jose	`6.1.0` → `6.2.3`
wrangler (source)	`4.59.1` → `4.87.0`

Release Notes

cloudflare/workerd (@cloudflare/workers-types)

honojs/hono (hono)

`v4.12.16`

Compare Source

`v4.12.15`

Compare Source

What's Changed

fix(jwt): support single-line PEM keys by @hiendv in #4889

New Contributors

@hiendv made their first contribution in #4889

Full Changelog: honojs/hono@v4.12.14...v4.12.15

panva/jose (jose)

`v6.2.3`

Compare Source

Refactor

cleanly reject invalid PBES2 p2c (0cdb851)

`v6.2.2`

Compare Source

Fixes

reject failed decompression with JWEInvalid error (043b181)

`v6.2.1`

Compare Source

Refactor

reorganize internals, less files, smaller footprint (d4231f9)

`v6.2.0`

Compare Source

Features

re-introduce JWE "zip" (Compression Algorithm) Header Parameter support (b13b446)

Documentation

clarify return of general jws and jwe (56682b4)

`v6.1.3`

Compare Source

Refactor

avoid export * as for google closure's compiler sake (6303d98), closes #832

`v6.1.2`

Compare Source

Refactor

fallback to checking instanceof for CryptoKey (901cd90), closes #765 #803 #821 #827 #828

`v6.1.1`

Compare Source

Documentation

add link to RFC9864 (767edde)
link to ML-DSA for JOSE (ed4252c)
remove mention of Edge Runtime from the readme (94fdde7)
update README.md (25098ef)

Refactor

eliminate named exports in the source code (f6ae30d)
expose setKeyManagementParameters also on a GeneralEncrypt Recipient (16e6b23)
faster path for symmetric key checks (a44c2ec)
improve en/decoding overheads (daee426)

cloudflare/workers-sdk (wrangler)

`v4.87.0`

Compare Source

Minor Changes

#13726 b5ac54b Thanks @penalosa! - Hard fail on Node.js < 22

Wrangler no longer supports Node.js 20.x, as it reached end-of-life on 2026-04-30. The minimum supported Node.js version is now 22.0.0. See https://github.com/nodejs/release?tab=readme-ov-file#end-of-life-releases.
#13717 9a1f014 Thanks @NuroDev! - Add an experimental experimental_generateTypes() programmatic API.

Wrangler now exposes experimental_generateTypes() from the package root so you can generate Worker types in code using the same logic as wrangler types. The API supports the same core type-generation options (include env/runtime toggles) and returns structured output with separate env and runtime content alongside the combined formatted output.

Patch Changes

#13732 22e1a61 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260426.1 1.20260429.1
#13754 00523c8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260429.1 1.20260430.1
#13711 1c4d850 Thanks @dario-piotrowicz! - fix: skip auto-config and OpenNext delegation when --config is explicitly provided

When --config is passed to wrangler deploy, the user is explicitly targeting a specific Worker configuration. Previously, wrangler would ignore --config and delegate to opennextjs-cloudflare deploy if it detected an OpenNext project in the working directory, silently deploying the wrong Worker. Now, both auto-config detection and OpenNext delegation are skipped when --config is provided, matching the existing behavior for --script and --assets.
#13735 6d28037 Thanks @edmundhung! - Improve config-schema.json hover text in more editors

Wrangler now emits markdownDescription in config-schema.json alongside the existing description field. Editors that support rich JSON Schema hovers can use that markdown directly instead of rendering escaped links and formatting.
#13722 0827815 Thanks @MattieTK! - Improve safe telemetry categorisation for user-facing Wrangler errors.
#13116 e539008 Thanks @dario-piotrowicz! - Allow getPlatformProxy and unstable_getMiniflareWorkerOptions to start when the assets directory does not exist yet

Previously, getPlatformProxy would catch and swallow NonExistentAssetsDirError internally when the configured assets directory was absent on disk. This has been refactored so that the directory-existence check is skipped entirely for getPlatformProxy and unstable_getMiniflareWorkerOptions, since these APIs are typically used at dev time in frameworks where the assets directory is a build output that may not exist yet.

wrangler dev, wrangler deploy, wrangler versions upload, and wrangler triggers deploy continue to require the assets directory to exist when specified.
Updated dependencies [22e1a61, 00523c8, b5ac54b, e653edf, e1eff94, e539008, 0bf64a7, b04eedf, 6457fb3, c07d0cb]:
- miniflare@4.20260430.0
- @cloudflare/kv-asset-handler@0.5.0

`v4.86.0`

Compare Source

Minor Changes

#13605 ea943ff Thanks @danielgek! - Add namespace support to wrangler ai-search commands

All wrangler ai-search instance commands (create, list, get, update, delete, stats, search) now accept a --namespace (or -n) flag to target a specific AI Search namespace. When the flag is omitted, commands default to the default namespace that Cloudflare automatically provisions for every account.

wrangler ai-search list now displays a namespace column, and wrangler ai-search create offers an interactive picker for existing namespaces (with an option to create a new one) when --namespace is not supplied in an interactive session.

A new wrangler ai-search namespace subcommand group is also introduced, with list, create, get, update, and delete subcommands for managing namespaces directly.
```
wrangler ai-search list --namespace blog
wrangler ai-search create my-instance --namespace blog --type r2 --source my-bucket
wrangler ai-search namespace create blog --description "Blog content"
```
#13637 9eb9e69 Thanks @edmundhung! - Add --tunnel flag to wrangler dev for sharing your local dev server via Cloudflare Quick Tunnels

You can now expose your local dev server publicly by passing --tunnel:
```
wrangler dev --tunnel
```
This starts a Cloudflare Quick Tunnel that gives you a random *.trycloudflare.com URL to share. The tunnel stops automatically when the dev session ends. Quick tunnels don't require a Cloudflare account or any configuration.

A warning is shown when Server-Sent Events (SSE) responses are detected through the tunnel, since quick tunnels don't support SSE.
#13661 0a5db08 Thanks @aspizu! - wrangler tail will now log stack traces. These stack traces already include resolved frames if you have chosen to upload sourcemaps.
#13617 118027d Thanks @roerohan! - Force Flagship bindings to always use remote mode in local dev

Flagship bindings now always access the remote Flagship service during local development, matching the behavior of AI bindings. Previously, Flagship supported both local and remote modes, but the local stub only returned default values, providing no real functionality and creating a dual source of truth for flag evaluations.

The remote config field is retained for backward compatibility but only controls whether a warning is displayed. Setting remote: true suppresses the warning that Flagship bindings always access remote resources and may incur usage charges in local dev.
#13254 e867ac2 Thanks @tgarg-cf! - Add wrangler queues consumer list subcommands for listing queue consumers

Three new commands are available for listing consumers on a queue:
- wrangler queues consumer list <queue-name> — lists all consumers (both worker and HTTP pull), grouped by type
- wrangler queues consumer worker list <queue-name> — lists only worker consumers
- wrangler queues consumer http list <queue-name> — lists only HTTP pull consumers

Patch Changes

#13696 62e9f2a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260424.1 1.20260426.1
#13576 2dc6175 Thanks @MattieTK! - Restore telemetry tracking for common CLI flags that were unintentionally dropped during sanitisation

When argument sanitisation was introduced, only explicitly allow-listed args had their values included in telemetry. The allow list was very conservative, which meant common boolean flags like --remote, --json, --dry-run, --force, and many others were no longer being captured in sanitizedArgs despite previously being tracked. Boolean flags are inherently safe (values are only true/false), so these have now been added back to the global allow list. A small number of fixed-choice args (--local-protocol, --upstream-protocol, --containers-rollout) have also been added with their known value sets.
#13649 ae8eae3 Thanks @petebacondarwin! - Fix service binding and tail consumer props being dropped between workers in different local dev instances

When a service binding or tail consumer configured with props targeted a worker running in a separate wrangler dev instance (via the dev registry), the props were silently dropped and the remote entrypoint saw an empty ctx.props. Props are now forwarded correctly across the dev registry boundary, matching the behavior users get when all workers run in a single instance.

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate Bot added dependencies Pull requests that update a dependency file optional labels Oct 22, 2025

renovate Bot changed the title ~~fix(deps): upgrade dependency hono to v4.10.2~~ fix(deps): upgrade dependency hono to v4.10.2 - autoclosed Oct 22, 2025

renovate Bot closed this Oct 22, 2025

renovate Bot deleted the renovate/npm-packages branch October 22, 2025 15:47

renovate Bot changed the title ~~fix(deps): upgrade dependency hono to v4.10.2 - autoclosed~~ fix(deps): upgrade dependency wrangler to v4.45.0 Oct 23, 2025

renovate Bot reopened this Oct 23, 2025

renovate Bot force-pushed the renovate/npm-packages branch 3 times, most recently from 09b7a7b to c8e567a Compare October 28, 2025 13:39

renovate Bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.0~~ fix(deps): upgrade dependency wrangler to v4.45.1 Oct 28, 2025

renovate Bot force-pushed the renovate/npm-packages branch from c8e567a to 4b6a6d6 Compare October 29, 2025 18:44

renovate Bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.1~~ fix(deps): upgrade dependency wrangler to v4.45.2 Oct 29, 2025

renovate Bot force-pushed the renovate/npm-packages branch from 4b6a6d6 to 1accf23 Compare October 31, 2025 01:00

renovate Bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.2~~ fix(deps): upgrade dependency wrangler to v4.45.3 Oct 31, 2025

renovate Bot force-pushed the renovate/npm-packages branch from 1accf23 to 0a44c3f Compare November 4, 2025 17:47

renovate Bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.3~~ fix(deps): upgrade dependency wrangler to v4.45.4 Nov 4, 2025

renovate Bot force-pushed the renovate/npm-packages branch from 0a44c3f to e9edbfe Compare November 6, 2025 13:50

renovate Bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.45.4~~ fix(deps): upgrade dependency wrangler to v4.46.0 Nov 6, 2025

renovate Bot force-pushed the renovate/npm-packages branch from e9edbfe to 135c95c Compare November 6, 2025 20:31

renovate Bot changed the title ~~fix(deps): upgrade dependency wrangler to v4.46.0~~ fix(deps): upgrade npm packages Nov 6, 2025

renovate Bot force-pushed the renovate/npm-packages branch 7 times, most recently from e93bb6a to e8af37b Compare November 14, 2025 19:12

renovate Bot force-pushed the renovate/npm-packages branch 6 times, most recently from 74d799d to 2e23837 Compare December 2, 2025 21:37

renovate Bot force-pushed the renovate/npm-packages branch 5 times, most recently from 9cd2a4c to ee86b4d Compare December 10, 2025 08:35

renovate Bot force-pushed the renovate/npm-packages branch 7 times, most recently from 53c5700 to 7875075 Compare December 17, 2025 02:29

renovate Bot force-pushed the renovate/npm-packages branch 9 times, most recently from a40215c to 271af73 Compare December 25, 2025 05:38

renovate Bot force-pushed the renovate/npm-packages branch 2 times, most recently from de621fb to 8dfa850 Compare December 29, 2025 02:05

fix(deps): upgrade npm packages

24323a4

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): upgrade npm packages#19

fix(deps): upgrade npm packages#19
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-packages

renovate Bot commented Oct 22, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

New Contributors

Refactor

Fixes

Refactor

Features

Documentation

Refactor

Refactor

Documentation

Refactor

Minor Changes

Patch Changes

renovate Bot commented Oct 22, 2025 •

edited

Loading