Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 4, 2025

Bumps the npm-deps group with 3 updates: hono, @cloudflare/workers-types and wrangler.

Updates hono from 4.8.5 to 4.8.12

Release notes

Sourced from hono's releases.

v4.8.12

What's Changed

Full Changelog: honojs/hono@v4.8.11...v4.8.12

v4.8.11

What's Changed

Full Changelog: honojs/hono@v4.8.10...v4.8.11

v4.8.10

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.8.9...v4.8.10

v4.8.9

What's Changed

Full Changelog: honojs/hono@v4.8.8...v4.8.9

v4.8.8

What's Changed

Full Changelog: honojs/hono@v4.8.7...v4.8.8

v4.8.7

... (truncated)

Commits

Updates @cloudflare/workers-types from 4.20250719.0 to 4.20250803.0

Commits

Updates wrangler from 4.25.0 to 4.27.0

Release notes

Sourced from wrangler's releases.

wrangler@4.27.0

Minor Changes

  • #9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

    If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode, they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

    These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker. Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

    Further details:

    • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
    • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
    • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
    • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
    • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.

Patch Changes

  • #10051 0f7820e Thanks @​nikitassharma! - Add support for custom instance limits for containers. For example, instead of having to use the preconfigured dev/standard/basic instance types, you can now set:

    instance_type: {
      vcpu: 1,
      memory_mib: 1024,
      disk_mb: 4000
    }
    

    This feature is currently only available to customers on an enterprise plan.

  • #10149 e9bb8d3 Thanks @​vicb! - fix require("debug") in nodejs_compat mode

  • Updated dependencies [9b61f44]:

    • miniflare@4.20250730.0

wrangler@4.26.1

Patch Changes

  • #10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

    Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

    In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

  • #10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

  • #10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.27.0

Minor Changes

  • #9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

    If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode, they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

    These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker. Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

    Further details:

    • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
    • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
    • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
    • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
    • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.

Patch Changes

  • #10051 0f7820e Thanks @​nikitassharma! - Add support for custom instance limits for containers. For example, instead of having to use the preconfigured dev/standard/basic instance types, you can now set:

    instance_type: {
      vcpu: 1,
      memory_mib: 1024,
      disk_mb: 4000
    }
    

    This feature is currently only available to customers on an enterprise plan.

  • #10149 e9bb8d3 Thanks @​vicb! - fix require("debug") in nodejs_compat mode

  • Updated dependencies [9b61f44]:

    • miniflare@4.20250730.0

4.26.1

Patch Changes

  • #10061 f8a80a8 Thanks @​emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.

    Currently, if your container engine isn't set up to listen on unix:///var/run/docker.sock (or isn't symlinked to that), then you have to manually set this via the dev.containerEngine field in your Wrangler config, or via the env vars WRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaque internal errors thrown by the runtime when the daemon is not listening on unix:///var/run/docker.sock.

    In addition to WRANGLER_DOCKER_HOST, DOCKER_HOST can now also be used to set the container engine socket address.

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the npm-deps group with 3 updates: [hono](https://github.com/honojs/hono), [@cloudflare/workers-types](https://github.com/cloudflare/workerd) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).


Updates `hono` from 4.8.5 to 4.8.12
- [Release notes](https://github.com/honojs/hono/releases)
- [Commits](honojs/hono@v4.8.5...v4.8.12)

Updates `@cloudflare/workers-types` from 4.20250719.0 to 4.20250803.0
- [Release notes](https://github.com/cloudflare/workerd/releases)
- [Changelog](https://github.com/cloudflare/workerd/blob/main/Dockerfile.release)
- [Commits](https://github.com/cloudflare/workerd/commits)

Updates `wrangler` from 4.25.0 to 4.27.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.27.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: hono
  dependency-version: 4.8.12
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-deps
- dependency-name: "@cloudflare/workers-types"
  dependency-version: 4.20250803.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-deps
- dependency-name: wrangler
  dependency-version: 4.27.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 4, 2025
@shymega shymega merged commit cc3bbc8 into main Aug 11, 2025
0 of 4 checks passed
@shymega shymega deleted the dependabot/npm_and_yarn/npm-deps-3a60cf05b0 branch August 11, 2025 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants