Skip to content

chore(deps): update external fixes #53

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update external fixes #53

wants to merge 1 commit into from
+742 −243

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 19, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types 4.20250510.0 -> 4.20250525.0 age adoption passing confidence
esbuild 0.25.4 -> 0.25.5 age adoption passing confidence
mocha (source) 11.2.2 -> 11.5.0 age adoption passing confidence
semantic-release 24.2.3 -> 24.2.5 age adoption passing confidence
wrangler (source) 4.14.4 -> 4.17.0 age adoption passing confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20250525.0

Compare Source

v4.20250524.0

Compare Source

v4.20250523.0

Compare Source

v4.20250522.0

Compare Source

v4.20250521.0

Compare Source

v4.20250520.0

Compare Source

v4.20250519.0

Compare Source

v4.20250517.0

Compare Source

v4.20250515.0

Compare Source

v4.20250514.0

Compare Source

v4.20250513.0

Compare Source

evanw/esbuild (esbuild)

v0.25.5

Compare Source

  • Fix a regression with browser in package.json (#​4187)

    The fix to #​4144 in version 0.25.3 introduced a regression that caused browser overrides specified in package.json to fail to override relative path names that end in a trailing slash. That behavior change affected the [email protected] package. This regression has been fixed, and now has test coverage.

  • Add support for certain keywords as TypeScript tuple labels (#​4192)

    Previously esbuild could incorrectly fail to parse certain keywords as TypeScript tuple labels that are parsed by the official TypeScript compiler if they were followed by a ? modifier. These labels included function, import, infer, new, readonly, and typeof. With this release, these keywords will now be parsed correctly. Here's an example of some affected code:

    type Foo = [
  value: any,
  readonly?: boolean, // This is now parsed correctly
]

  • Add CSS prefixes for the stretch sizing value (#​4184)

    This release adds support for prefixing CSS declarations such as div { width: stretch }. That CSS is now transformed into this depending on what the --target= setting includes:

    div {
  width: -webkit-fill-available;
  width: -moz-available;
  width: stretch;
}
mochajs/mocha (mocha)

v11.5.0

Compare Source

🌟 Features

v11.4.0

Compare Source

🌟 Features
📚 Documentation
  • added CHANGELOG.md note around 11.1 yargs-parser update (#​5362) (618415d)

v11.3.0

Compare Source

🌟 Features
📚 Documentation
🧹 Chores
semantic-release/semantic-release (semantic-release)

v24.2.5

Compare Source

v24.2.4

Compare Source

cloudflare/workers-sdk (wrangler)

v4.17.0

Minor Changes

  • #​9321 6c03bde Thanks @​petebacondarwin! - Add support for FedRAMP High compliance region

    Now it is possible to target Wrangler at the FedRAMP High compliance region.
    There are two ways to signal to Wrangler to run in this mode:

    • set "compliance_region": "fedramp_high" in a Wrangler configuration
    • set CLOUDFLARE_COMPLIANCE_REGION=fedramp_high environment variable when running Wrangler

    If both are provided and the values do not match then Wrangler will exit with an error.

    When in this mode OAuth authentication is not supported.
    It is necessary to authenticate using a Cloudflare API Token acquired from the Cloudflare FedRAMP High dashboard.

    Most bindings and commands are supported in this mode.

    • Unsupported commands may result in API requests that are not supported - possibly 422 Unprocessable Entity responses.
    • Unsupported bindings may work in local dev, as there is no local validation, but will fail at Worker deployment time.

    Resolves DEVX-1921.

  • #​9330 34c71ce Thanks @​edmundhung! - Updated internal configuration to use Miniflare’s new defaultPersistRoot instead of per-plugin persist flags

  • #​8973 cc7fae4 Thanks @​Caio-Nogueira! - Show latest instance by default on workflows instances describe command

Patch Changes

v4.16.1

Compare Source

Patch Changes

v4.16.0

Compare Source

Minor Changes

  • #​9288 3b8f7f1 Thanks @​petebacondarwin! - allow --name and --env args on wrangler deploy

    Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
    Now specifying --name is supported and will override any names set in the Wrangler config:

    wrangler.json

    {
	"name": "config-worker"
	"env": {
		"staging": { "name": "config-worker-env" }
	}
}
    Command Previous (Worker name) Proposed (Worker name) Comment
    wrangler deploy --name=args-worker "args-worker" "args-worker" CLI arg used
    wrangler deploy --name=args-worker --env=staging Error "args-worker" CLI arg used
    wrangler deploy --name=args-worker --env=prod Error "args-worker" CLI arg used
    wrangler deploy "config-worker" "config-worker" Top-level config used
    wrangler deploy --env=staging "config-worker-env" "config-worker-env" Named env config used
    wrangler deploy --env=prod "config-worker-prod" "config-worker-prod" CLI arg and top-level config combined

  • #​9265 16de0d5 Thanks @​edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

  • #​9234 2fe6219 Thanks @​emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

  • #​9269 66d975e Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

    Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

    Also include the ai binding since the bindings is already remote by default anyways.

  • #​9151 5ab035d Thanks @​gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

  • #​9231 02d40ed Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

    Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

    Also include the ai binding since the bindings is already remote by default anyways.

  • #​9221 2ef31a9 Thanks @​vicb! - bump @cloudflare/unenv-preset

  • #​9277 db5ea8f Thanks @​penalosa! - Support Mixed Mode for more binding types

  • #​9266 f2a16f1 Thanks @​petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

  • #​9245 b87b472 Thanks @​penalosa! - Support Mixed Mode Dispatch Namespaces

  • Updated dependencies [db5ea8f, b87b472]:

v4.15.2

Compare Source

Patch Changes

v4.15.1

Compare Source

Patch Changes

v4.15.0

Compare Source

Minor Changes

  • #​8794 02f0699 Thanks @​eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Fetcher;
}

    This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}

  • #​8716 63a6504 Thanks @​ItsWendell! - add --metafile flag to generate esbuild metadata file during build

  • #​9122 f17ee08 Thanks @​avenceslau! - Unhide wrangler workflows delete command

Patch Changes

Configuration

📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 renovate bot force-pushed the renovate-external-fixes branch 10 times, most recently from ff9a059 to 665fccc Compare May 25, 2025 04:25
@renovate renovate bot force-pushed the renovate-external-fixes branch from 665fccc to 41bfad1 Compare May 27, 2025 05:12
@renovate renovate bot force-pushed the renovate-external-fixes branch from 41bfad1 to 409cb4b Compare May 27, 2025 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants