chore(deps): Bump the npm-minor-and-patch group with 5 updates

[dependabot]

Bumps the npm-minor-and-patch group with 5 updates:

Package	From	To
@tightknitai/block-kitchen	0.10.2	0.10.11
hono	4.13.1	4.13.2
@cloudflare/vite-plugin	1.51.2	1.52.1
@cloudflare/workers-types	5.20260810.1	5.20260817.1
wrangler	4.120.1	4.123.0

Updates @tightknitai/block-kitchen from 0.10.2 to 0.10.11

Release notes

Sourced from @​tightknitai/block-kitchen's releases.

block-kitchen: v0.10.11

0.10.11 (2026-08-17)

Bug Fixes

• close the block hover toolbar after a drag-reorder (ccbd968)
• close the block hover toolbar after a drag-reorder (479ffcd)

---

This PR was generated with Release Please. See documentation.

block-kitchen: v0.10.10

0.10.10 (2026-08-17)

Features

• make the Slack channel picker a type-to-filter combobox (bd1f878)
• make the Slack channel picker a type-to-filter combobox (017eaef)

---

This PR was generated with Release Please. See documentation.

block-kitchen: v0.10.9

0.10.9 (2026-08-17)

Features

• editors: let image blocks switch between URL and Slack file sources (b86581e)
• editors: let image blocks switch between URL and Slack file sources (882d55a)

---

This PR was generated with Release Please. See documentation.

block-kitchen: v0.10.8

0.10.8 (2026-08-16)

Features

• palette: add header, divider and image to simple mode (08dc19f)
• palette: collapsible desktop rail, tighter rows, steadier mobile sheet (4f2bc70)

... (truncated)

Changelog

Sourced from @​tightknitai/block-kitchen's changelog.

0.10.11 (2026-08-17)

Bug Fixes

• close the block hover toolbar after a drag-reorder (ccbd968)
• close the block hover toolbar after a drag-reorder (479ffcd)

0.10.10 (2026-08-17)

Features

• make the Slack channel picker a type-to-filter combobox (bd1f878)
• make the Slack channel picker a type-to-filter combobox (017eaef)

0.10.9 (2026-08-17)

Features

• editors: let image blocks switch between URL and Slack file sources (b86581e)
• editors: let image blocks switch between URL and Slack file sources (882d55a)

0.10.8 (2026-08-16)

Features

• palette: add header, divider and image to simple mode (08dc19f)
• palette: collapsible desktop rail, tighter rows, steadier mobile sheet (4f2bc70)
• palette: collapsible desktop rail, tighter rows, steadier mobile sheet (4114e1d)

Bug Fixes

• deps: update slack-blocks-to-jsx to 1.1.2 (01e742c)
• palette: trail the sheet row's chevron instead of leading with it (1af7ce4)

0.10.7 (2026-08-15)

Features

• toolbar: collapse Clear and View JSON to icons that expand on hover (2dfeade)

Bug Fixes

• layout: scroll the palette instead of stretching the host page (0298118)

... (truncated)

Commits

• 410e84f Merge pull request #197 from TightknitAI/release-please--branches--main--comp...
• acd5add chore(main): release block-kitchen 0.10.11
• 547110f Merge pull request #179 from TightknitAI/dependabot/npm_and_yarn/nanoid-6.0.1
• ccbd968 Merge pull request #196 from TightknitAI/claude/block-reorder-focus-menu-11f1c4
• 479ffcd fix: close the block hover toolbar after a drag-reorder
• 074328d Merge pull request #195 from TightknitAI/release-please--branches--main--comp...
• 282f4e6 chore(main): release block-kitchen 0.10.10
• bd1f878 Merge pull request #194 from TightknitAI/claude/slack-channel-picker-combobox...
• 017eaef feat: make the Slack channel picker a type-to-filter combobox
• 6471e4b Merge pull request #193 from TightknitAI/release-please--branches--main--comp...
• Additional commits viewable in compare view

Updates hono from 4.13.1 to 4.13.2

Release notes

Sourced from hono's releases.

v4.13.2

What's Changed

• fix(secure-headers): output standard empty parentheses () instead of none for disabled Permissions-Policy directives in honojs/hono#5197
• fix(jsx): render async children of document metadata tags instead of [object Promise] in honojs/hono#5204
• fix(etag): resolve incorrect incremental hashing for chunked responses in honojs/hono#5199
• fix(client): serialize multiple cookies correctly in honojs/hono#5202
• fix(etag): stabilize digest across stream chunks in honojs/hono#5205
• fix(url): strip trailing question mark correctly for optional params with regex quantifiers in honojs/hono#5209
• perf(cors): pre-join static array header options during initialization in honojs/hono#5210
• fix(client): send falsy JSON bodies in honojs/hono#5215
• feat(secure-headers): add missing W3C Permissions-Policy directives in honojs/hono#5214

Full Changelog: honojs/hono@v4.13.1...v4.13.2

Commits

• 41bdc42 4.13.2
• 6ea514d feat(secure-headers): add missing W3C Permissions-Policy directives (#5214)
• 329b6f4 fix(client): send falsy JSON bodies (#5215)
• a1e4ac7 perf(cors): pre-join static array header options during initialization (#5210)
• d982f63 fix(url): strip trailing question mark correctly for optional params with reg...
• 26de731 fix(etag): stabilize digest across stream chunks (#5205)
• 7075369 Revert " fix(etag): resolve incorrect incremental hashing for chunked respons...
• f2a72d3 fix(client): serialize multiple cookies correctly (#5202)
• 8a5852d fix(etag): resolve incorrect incremental hashing for chunked responses (#5199)
• 765d13b fix(jsx): render async children of document metadata tags instead of [object ...
• Additional commits viewable in compare view

Updates @cloudflare/vite-plugin from 1.51.2 to 1.52.1

Release notes

Sourced from @​cloudflare/vite-plugin's releases.

@​cloudflare/vite-plugin@​1.52.1

Patch Changes

• Updated dependencies [b8fd112, f0f2054, 339509d]:
  • miniflare@5.20260811.1-alpha
  • wrangler@4.123.0

@​cloudflare/vite-plugin@​1.52.0

Minor Changes

• #15123 d0c976c Thanks @​dependabot! - Detect Node.js compatibility from the compatibility date, now that nodejs_compat is enabled by default

  As of compatibility date 2026-08-04, workerd enables the nodejs_compat and nodejs_compat_v2 compatibility flags by default. Previously these tools only treated Node.js compatibility as enabled when one of those flags was listed explicitly, so a Worker on a compatibility date of 2026-08-04 or later without the flag would get Node.js APIs from the runtime but no Node.js polyfills from the bundler, and process.env could be substituted with an empty object at build time. They now resolve these flags the same way workerd does, and honour no_nodejs_compat to opt out.

  To keep Node.js compatibility switched off on a newer compatibility date, specify both no_nodejs_compat and no_nodejs_compat_v2, since each flag has its own default.

  @cloudflare/vitest-pool-workers needs nodejs_compat_v2 for its own test runner, so it continues to override a project that opts out of it. On a compatibility date that enables the flag anyway, it now drops the opt-out rather than adding the flag back, which workerd would reject — previously this stopped such a project from running any tests at all.

  wrangler types also no longer attributes its @types/node suggestion to "the nodejs_compat flag", which it can now make for Workers that do not set the flag at all.

Patch Changes

• #15148 0b82b15 Thanks @​jamesopstad! - Ignore a nodejs_compat compatibility flag that the compatibility date already enables

  workerd rejects a compatibility flag that its compatibility date enables by default, so a Worker configured with both a compatibility date of 2026-08-04 or later and nodejs_compat failed to start locally with "The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore".

  The redundant nodejs_compat and nodejs_compat_v2 flags are now dropped when starting the runtime, which has no effect on the resulting Worker because the compatibility date enables both anyway. no_nodejs_compat and no_nodejs_compat_v2 still switch Node.js compatibility off, and a flag specified alongside its own opt-out is left alone so that workerd still reports those as contradictory.

• Updated dependencies [d0c976c, d0c976c, 0b82b15, d0c976c, d0c976c, 90dd5e5, 3b02915]:

  • miniflare@5.20260811.0-alpha
  • wrangler@4.122.0

@​cloudflare/vite-plugin@​1.51.3

Patch Changes

• Updated dependencies [15cad03, 026e058, 731b33a, e1b5b4b, 5b1b930, 6e7d37d, d669088, 15cad03, c7aede7, 0aa8fa5]:
  • wrangler@4.121.0
  • miniflare@5.20260804.1-alpha

Changelog

Sourced from @​cloudflare/vite-plugin's changelog.

1.52.1

Patch Changes

• Updated dependencies [b8fd112, f0f2054, 339509d]:
  • miniflare@5.20260811.1-alpha
  • wrangler@4.123.0

1.52.0

Minor Changes

• #15123 d0c976c Thanks @​dependabot! - Detect Node.js compatibility from the compatibility date, now that nodejs_compat is enabled by default

  As of compatibility date 2026-08-04, workerd enables the nodejs_compat and nodejs_compat_v2 compatibility flags by default. Previously these tools only treated Node.js compatibility as enabled when one of those flags was listed explicitly, so a Worker on a compatibility date of 2026-08-04 or later without the flag would get Node.js APIs from the runtime but no Node.js polyfills from the bundler, and process.env could be substituted with an empty object at build time. They now resolve these flags the same way workerd does, and honour no_nodejs_compat to opt out.

  To keep Node.js compatibility switched off on a newer compatibility date, specify both no_nodejs_compat and no_nodejs_compat_v2, since each flag has its own default.

  @cloudflare/vitest-pool-workers needs nodejs_compat_v2 for its own test runner, so it continues to override a project that opts out of it. On a compatibility date that enables the flag anyway, it now drops the opt-out rather than adding the flag back, which workerd would reject — previously this stopped such a project from running any tests at all.

  wrangler types also no longer attributes its @types/node suggestion to "the nodejs_compat flag", which it can now make for Workers that do not set the flag at all.

Patch Changes

• #15148 0b82b15 Thanks @​jamesopstad! - Ignore a nodejs_compat compatibility flag that the compatibility date already enables

  workerd rejects a compatibility flag that its compatibility date enables by default, so a Worker configured with both a compatibility date of 2026-08-04 or later and nodejs_compat failed to start locally with "The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore".

  The redundant nodejs_compat and nodejs_compat_v2 flags are now dropped when starting the runtime, which has no effect on the resulting Worker because the compatibility date enables both anyway. no_nodejs_compat and no_nodejs_compat_v2 still switch Node.js compatibility off, and a flag specified alongside its own opt-out is left alone so that workerd still reports those as contradictory.

• Updated dependencies [d0c976c, d0c976c, 0b82b15, d0c976c, d0c976c, 90dd5e5, 3b02915]:

  • miniflare@5.20260811.0-alpha
  • wrangler@4.122.0

1.51.3

Patch Changes

• Updated dependencies [15cad03, 026e058, 731b33a, e1b5b4b, 5b1b930, 6e7d37d, d669088, 15cad03, c7aede7, 0aa8fa5]:
  • wrangler@4.121.0
  • miniflare@5.20260804.1-alpha

Commits

• c576a82 Version Packages (#15154)
• e5d56e9 Version Packages (#15145)
• 15fc568 Version Packages (#15118)
• See full diff in compare view

Updates @cloudflare/workers-types from 5.20260810.1 to 5.20260817.1

Commits

• See full diff in compare view

Updates wrangler from 4.120.1 to 4.123.0

Release notes

Sourced from wrangler's releases.

wrangler@4.123.0

Minor Changes

• #15113 b8fd112 Thanks @​BSFishy! - Add local dev simulation for Cloudflare Access ctx.access.getIdentity()

  You can now configure a mock Cloudflare Access identity in wrangler.json so that ctx.access.getIdentity() returns it during local development.

  // wrangler.json
  {
    "access": {
      "dev": {
        "aud": "my-app-aud-tag",
        "identity": {
          "email": "user@example.com",
          "name": "Test User"
        }
      }
    }
  }

• #15152 f0f2054 Thanks @​GregBrimble! - [private beta]: Updates the --ignore-defaults flag to --ignore-base-config on wrangler preview commands.

  --ignore-base-config now only takes effect on Preview creation, rather than on each deployment, since Preview base configuration is now copy-on-create rather than inherit-on-deploy.

• #14872 339509d Thanks @​dario-piotrowicz! - Add automatic update prompts for out-of-date Cloudflare agent skills

  When Cloudflare skills were previously installed by Wrangler and the upstream cloudflare/skills repository has newer content, Wrangler now offers to update them after eligible commands complete.

  To reduce prompt fatigue, the update check only runs once a month (30 days since the last install or update). Declining suppresses the prompt until the next upstream change.

  When declining an update, Wrangler offers the option to permanently disable future update prompts. This preference is stored globally in ~/.wrangler/agents-skills-install.jsonc. The WRANGLER_NO_SKILLS_UPDATE_PROMPTS=true environment variable can also be used to suppress prompts. The --install-skills flag remains available regardless of these settings.

Patch Changes

• Updated dependencies [b8fd112]:
  • miniflare@5.20260811.1-alpha

wrangler@4.122.0

Minor Changes

• #15123 d0c976c Thanks @​dependabot! - Detect Node.js compatibility from the compatibility date, now that nodejs_compat is enabled by default

  As of compatibility date 2026-08-04, workerd enables the nodejs_compat and nodejs_compat_v2 compatibility flags by default. Previously these tools only treated Node.js compatibility as enabled when one of those flags was listed explicitly, so a Worker on a compatibility date of 2026-08-04 or later without the flag would get Node.js APIs from the runtime but no Node.js polyfills from the bundler, and process.env could be substituted with an empty object at build time. They now resolve these flags the same way workerd does, and honour no_nodejs_compat to opt out.

  To keep Node.js compatibility switched off on a newer compatibility date, specify both no_nodejs_compat and no_nodejs_compat_v2, since each flag has its own default.

  @cloudflare/vitest-pool-workers needs nodejs_compat_v2 for its own test runner, so it continues to override a project that opts out of it. On a compatibility date that enables the flag anyway, it now drops the opt-out rather than adding the flag back, which workerd would reject — previously this stopped such a project from running any tests at all.

... (truncated)

Commits

• c576a82 Version Packages (#15154)
• 339509d Add automatic update prompts for out-of-date Cloudflare agent skills (#14872)
• b8fd112 feat: implement local dev for ctx.access (#15113)
• f0f2054 Replace ignore-defaults with ignore-base-config CLI arg for Previews (#15152)
• e5d56e9 Version Packages (#15145)
• 3b02915 [wrangler] Avoid stale remote binding sessions (#15142)
• d0c976c Bump the workerd-and-workers-types group across 1 directory with 2 updates (#...
• 15fc568 Version Packages (#15118)
• 5b1b930 Fetch script metadata directly instead of listing all scripts (#15132)
• 0aa8fa5 Support DO_NOT_TRACK=1 (#14924)
• Additional commits viewable in compare view

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 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

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}