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

[dependabot]

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

Package	From	To
@tightknitai/block-kitchen	0.8.6	0.9.8
@tightknitai/slack-block-kit-validator	0.1.8	0.1.10
hono	4.12.26	4.12.27
slack-web-api-client	1.1.13	1.1.14
@cloudflare/vite-plugin	1.42.0	1.43.0
@cloudflare/workers-types	4.20260617.1	4.20260702.1
@vitejs/plugin-react	6.0.2	6.0.3
vite	8.0.16	8.1.3
wrangler	4.102.0	4.107.0

Updates @tightknitai/block-kitchen from 0.8.6 to 0.9.8

Release notes

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

block-kitchen: v0.9.8

0.9.8 (2026-07-02)

Bug Fixes

• drop preview_images from data_visualization blocks on retrieval (8706a80)
• sanitize: drop retrieval-only preview_images from data_visualization (5ed158c)

block-kitchen: v0.9.7

0.9.7 (2026-07-02)

Bug Fixes

• styles: scope bk-utilities layer to .bk-root / .bk-portal-content (c12ee96)
• styles: scope bk-utilities layer to .bk-root / .bk-portal-content (f91db17)

block-kitchen: v0.9.6

0.9.6 (2026-07-02)

Features

• editing: pre-load a message into edit mode via editing.initialTarget (aa73bf6)
• editing: pre-load a message into edit mode via editing.initialTarget (a7ed7e8)

block-kitchen: v0.9.5

0.9.5 (2026-07-01)

Bug Fixes

• load-dialog: rename find button to "Load message" (ae78d23)
• load-dialog: rename find button to "Load message" (f0228b3)

block-kitchen: v0.9.4

0.9.4 (2026-07-01)

Features

• json-drawer: add a copy-to-clipboard button on the JSON pane (949f8c5)
• load-dialog: make recent-message previews select-then-load (3a815ae)
• load-dialog: rename Load/Edit copy to Find (0bd5d40)
• load-dialog: shape recent-message previews like Slack messages (d9f0cd1)
• load-dialog: surface Slack sign-in in the find dialog (9736c06)
• update-dialog: add Slack sign-in button with background polling (d144fff)
• update-dialog: Slack sign-in button with background polling (cf2bb4b)

... (truncated)

Changelog

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

0.9.8 (2026-07-02)

Bug Fixes

• drop preview_images from data_visualization blocks on retrieval (8706a80)
• sanitize: drop retrieval-only preview_images from data_visualization (5ed158c)

0.9.7 (2026-07-02)

Bug Fixes

• styles: scope bk-utilities layer to .bk-root / .bk-portal-content (c12ee96)
• styles: scope bk-utilities layer to .bk-root / .bk-portal-content (f91db17)

0.9.6 (2026-07-02)

Features

• editing: pre-load a message into edit mode via editing.initialTarget (aa73bf6)
• editing: pre-load a message into edit mode via editing.initialTarget (a7ed7e8)

0.9.5 (2026-07-01)

Bug Fixes

• load-dialog: rename find button to "Load message" (ae78d23)
• load-dialog: rename find button to "Load message" (f0228b3)

0.9.4 (2026-07-01)

Features

• json-drawer: add a copy-to-clipboard button on the JSON pane (949f8c5)
• load-dialog: make recent-message previews select-then-load (3a815ae)
• load-dialog: rename Load/Edit copy to Find (0bd5d40)
• load-dialog: shape recent-message previews like Slack messages (d9f0cd1)
• load-dialog: surface Slack sign-in in the find dialog (9736c06)
• update-dialog: add Slack sign-in button with background polling (d144fff)
• update-dialog: Slack sign-in button with background polling (cf2bb4b)

Bug Fixes

• load-dialog: hide "open as new" for no-match verdicts (6f92686)
• load-dialog: stop clipping the selected-row outline (53079f1)

... (truncated)

Commits

• fe44ed6 Merge pull request #145 from TightknitAI/release-please--branches--main--comp...
• f685e64 chore(main): release block-kitchen 0.9.8
• 8706a80 Merge pull request #144 from TightknitAI/claude/data-viz-preview-images-jj5aaz
• 5ed158c fix(sanitize): drop retrieval-only preview_images from data_visualization
• 0898523 build(deps-dev): Bump the dev-dependencies group with 23 updates (#142)
• 30f60b4 build(deps-dev): Bump the dev-dependencies group in /demo with 4 updates (#141)
• 9624730 Merge pull request #140 from TightknitAI/release-please--branches--main--comp...
• 2746c46 chore(main): release block-kitchen 0.9.7
• c12ee96 Merge pull request #139 from TightknitAI/claude/adoring-galileo-7c17d7
• 8e10dae test(styles): cover scope-utilities build step
• Additional commits viewable in compare view

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

Updates @tightknitai/slack-block-kit-validator from 0.1.8 to 0.1.10

Release notes

Sourced from @​tightknitai/slack-block-kit-validator's releases.

slack-block-kit-validator: v0.1.10

0.1.10 (2026-07-01)

Features

• add data_table block support and surface-rule drift check (ENG-5108) (#55) (68ba572)

slack-block-kit-validator: v0.1.9

0.1.9 (2026-06-29)

Features

• support the new container block (#52) (cbce02c)

Bug Fixes

• ci: run release-please with a dedicated token (#50) (a49202c)
• ci: use default GITHUB_TOKEN for release-please (#53) (50d204e)

Changelog

Sourced from @​tightknitai/slack-block-kit-validator's changelog.

0.1.10 (2026-07-01)

Features

• add data_table block support and surface-rule drift check (ENG-5108) (#55) (68ba572)

0.1.9 (2026-06-29)

Features

• support the new container block (#52) (cbce02c)

Bug Fixes

• ci: run release-please with a dedicated token (#50) (a49202c)
• ci: use default GITHUB_TOKEN for release-please (#53) (50d204e)

Commits

• 6e94146 chore(main): release slack-block-kit-validator 0.1.10 (#56)
• 68ba572 feat: add data_table block support and surface-rule drift check (ENG-5108) (#55)
• da2f691 chore(main): release slack-block-kit-validator 0.1.9 (#54)
• 50d204e fix(ci): use default GITHUB_TOKEN for release-please (#53)
• 375484c chore(deps): Bump actions/checkout from 6 to 7 (#51)
• cbce02c feat: support the new container block (#52)
• a49202c fix(ci): run release-please with a dedicated token (#50)
• 264f768 chore(deps-dev): Bump vite from 6.4.2 to 6.4.3 in /demo (#49)
• 03b1f3b chore(deps): Bump codecov/codecov-action from 6 to 7 (#46)
• See full diff in compare view

Updates hono from 4.12.26 to 4.12.27

Release notes

Sourced from hono's releases.

v4.12.27

Security fixes

This release includes fixes for the following security issues:

hono/jsx does not isolate context per request

Affects: hono/jsx, hono/jsx-renderer. During SSR, context was stored process-wide instead of per request, so useContext()/useRequestContext() read after an await in an async component could return another concurrent request's value — leading to cross-request data disclosure or authorization checks against the wrong request. GHSA-hvrm-45r6-mjfj

Server-Side XSS via JSX escaping bypass in cx()

Affects: hono/css. cx() marked its composed class name as already-escaped without escaping the input, so untrusted input passed as a class name could break out of the JSX class attribute during SSR and inject markup (XSS). GHSA-w62v-xxxg-mg59

API Gateway v1 adapter can drop a repeated request header value

Affects: hono/aws-lambda. The API Gateway v1 (and VPC Lattice) adapter de-duplicated repeated header values by substring instead of exact match, dropping a value that is a substring of another (e.g. 203.0.113.1 dropped when 203.0.113.10 is present) — affecting logic such as X-Forwarded-For-based IP restriction. GHSA-xgm2-5f3f-mvvc

---

Users of hono/jsx/hono/jsx-renderer, hono/css (cx()), or the hono/aws-lambda API Gateway v1 / VPC Lattice adapters are encouraged to upgrade.

Commits

• 97c6fe1 4.12.27
• aa92177 Merge commit from fork
• cd3f6f7 Merge commit from fork
• d4853a8 fix(jsx): make merged context-isolation tests pass tsc type check (#5037)
• 6735fea fix(jsx): cast awaitedFallback through unknown to fix Deno type check (#5036)
• fab3b13 Merge commit from fork
• 9f0dadf ci: use npm Staged publishing (#5035)
• See full diff in compare view

Updates slack-web-api-client from 1.1.13 to 1.1.14

Release notes

Sourced from slack-web-api-client's releases.

v1.1.14

• Add streaming chunk, entity unfurl, and assistant loading_messages types (#55)
• Add support for the container block (#65)
• Dependency bumps (#42, #59, #60, #61, #62, #63)

Commits

• 6edee31 version 1.1.14 (#66)
• f2f565e feat(types): streaming chunks, entity unfurls, assistant loading_messages (#55)
• d058588 Bump actions/setup-node from 4 to 6 (#42)
• 5136b66 Bump actions/checkout from 4 to 7 (#63)
• faa22a8 Bump @​vitest/coverage-v8 from 4.1.6 to 4.1.9 (#62)
• ed46a94 Bump knip from 6.13.1 to 6.17.1 (#61)
• bf89b25 Bump @​biomejs/biome from 2.4.15 to 2.5.0 (#60)
• 7ac0196 Bump vitest from 4.1.6 to 4.1.9 (#59)
• 3020363 Add support for the container block (#65)
• See full diff in compare view

Updates @cloudflare/vite-plugin from 1.42.0 to 1.43.0

Release notes

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

@​cloudflare/vite-plugin@​1.43.0

Minor Changes

• #14382 fd92d56 Thanks @​petebacondarwin! - Add support for declarative Durable Object exports

  wrangler deploy now accepts an exports map in wrangler.json as a declarative alternative to the legacy migrations array.

  Each entry in exports is keyed by Durable Object class name. type carries the export kind (currently always "durable-object"); the state field carries the lifecycle and defaults to "created" (live) when omitted:

  {
    "exports": {
      // Provision a new Durable Object class (`MyDO`)
      "MyDO": { "type": "durable-object", "storage": "sqlite" },
      // Delete Durable Object class (`OldGone`)
      "OldGone": { "type": "durable-object", "state": "deleted" },
      // Rename a Durable Object class (from `OldName` to `NewName`)
      "OldName": {
        "type": "durable-object",
        "state": "renamed",
        "renamed_to": "NewName"
      },
      "NewName": { "type": "durable-object", "storage": "sqlite" },
      // Transfer a Durable Object (`Outgoing`) to a new Worker (`target-worker`)
      "Outgoing": {
        "type": "durable-object",
        "state": "transferred",
        "transferred_to": "target-worker"
      },
      // Prepare to receive the transfer of a Durable Object (`Incoming`) from another Worker (`source-worker`)
      "Incoming": {
        "type": "durable-object",
        "state": "expecting-transfer",
        "storage": "sqlite",
        "transfer_from": "source-worker"
      }
    }
  }

  When a Worker declares Durable Object class bindings but no lifecycle for them (neither a migrations array nor an exports map), wrangler warns and now suggests a declarative exports entry for each class (previously it suggested a legacy migrations block).

  The deployment response now surfaces the server's reconciliation result — created namespaces, applied tombstones, structured per-scenario info entries, and a removable_entries hint for stale tombstones that are safe to delete from the config. Blocking errors return the structured per-class detail with scenario tags, suggested remediation, and any referencing-script context.

  wrangler versions upload also forwards exports. Declarative exports lifecycle changes are reconciled when the version is deployed (wrangler versions deploy or wrangler deploy), so a versions upload payload can declare new classes in exports without immediately provisioning them. An actor binding (durable_objects.bindings) to a class declared only in exports on the same versions upload is rejected with a clear error (code 100406) — the binding cannot be resolved until the namespace is provisioned. Either stage the new class via ctx.exports.X (no binding required) on versions upload and add the binding at deploy time, or use wrangler deploy to provision and bind in one step (the same constraint applies to the migrations flow).

  Multi-version deploys (wrangler versions deploy A@50% B@50%) where the selected versions disagree on declarative exports are rejected server-side with a clear message: deploy the version that changes exports at 100% first, then run the percentage-split deploy. This prevents traffic on one branch routing to code that references unprovisioned or just-deleted DO namespaces. Single-version (100%) deploys are unaffected.

  Local development (wrangler dev, vite dev and unstable_startWorker) reads Durable Object SQLite storage settings from the new exports field, so applications using the declarative flow get correct local-dev storage without needing to also declare a migrations block.

... (truncated)

Changelog

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

1.43.0

Minor Changes

• #14382 fd92d56 Thanks @​petebacondarwin! - Add support for declarative Durable Object exports

  wrangler deploy now accepts an exports map in wrangler.json as a declarative alternative to the legacy migrations array.

  Each entry in exports is keyed by Durable Object class name. type carries the export kind (currently always "durable-object"); the state field carries the lifecycle and defaults to "created" (live) when omitted:

  {
    "exports": {
      // Provision a new Durable Object class (`MyDO`)
      "MyDO": { "type": "durable-object", "storage": "sqlite" },
      // Delete Durable Object class (`OldGone`)
      "OldGone": { "type": "durable-object", "state": "deleted" },
      // Rename a Durable Object class (from `OldName` to `NewName`)
      "OldName": {
        "type": "durable-object",
        "state": "renamed",
        "renamed_to": "NewName"
      },
      "NewName": { "type": "durable-object", "storage": "sqlite" },
      // Transfer a Durable Object (`Outgoing`) to a new Worker (`target-worker`)
      "Outgoing": {
        "type": "durable-object",
        "state": "transferred",
        "transferred_to": "target-worker"
      },
      // Prepare to receive the transfer of a Durable Object (`Incoming`) from another Worker (`source-worker`)
      "Incoming": {
        "type": "durable-object",
        "state": "expecting-transfer",
        "storage": "sqlite",
        "transfer_from": "source-worker"
      }
    }
  }

  When a Worker declares Durable Object class bindings but no lifecycle for them (neither a migrations array nor an exports map), wrangler warns and now suggests a declarative exports entry for each class (previously it suggested a legacy migrations block).

  The deployment response now surfaces the server's reconciliation result — created namespaces, applied tombstones, structured per-scenario info entries, and a removable_entries hint for stale tombstones that are safe to delete from the config. Blocking errors return the structured per-class detail with scenario tags, suggested remediation, and any referencing-script context.

  wrangler versions upload also forwards exports. Declarative exports lifecycle changes are reconciled when the version is deployed (wrangler versions deploy or wrangler deploy), so a versions upload payload can declare new classes in exports without immediately provisioning them. An actor binding (durable_objects.bindings) to a class declared only in exports on the same versions upload is rejected with a clear error (code 100406) — the binding cannot be resolved until the namespace is provisioned. Either stage the new class via ctx.exports.X (no binding required) on versions upload and add the binding at deploy time, or use wrangler deploy to provision and bind in one step (the same constraint applies to the migrations flow).

  Multi-version deploys (wrangler versions deploy A@50% B@50%) where the selected versions disagree on declarative exports are rejected server-side with a clear message: deploy the version that changes exports at 100% first, then run the percentage-split deploy. This prevents traffic on one branch routing to code that references unprovisioned or just-deleted DO namespaces. Single-version (100%) deploys are unaffected.

  Local development (wrangler dev, vite dev and unstable_startWorker) reads Durable Object SQLite storage settings from the new exports field, so applications using the declarative flow get correct local-dev storage without needing to also declare a migrations block.

... (truncated)

Commits

• 473e61f Version Packages (#14503)
• fd92d56 [wrangler] Add experimental support for declarative Durable Object exports (#...
• 13c69dd Version Packages (#14487)
• 75d8cb0 Revert "Version Packages" (#14490)
• 5e6950b Version Packages (#14433)
• 614ce10 feat(wrangler): apply d1 migrations with test harness (#14451)
• 8eacfd1 Replace all the occurrences of the deprecated toThrowError API with the app...
• 70d97d9 Version Packages (#14401)
• ec856a1 Version Packages (#14370)
• 4d8ffcb Version Packages (#14353)
• Additional commits viewable in compare view

Updates @cloudflare/workers-types from 4.20260617.1 to 4.20260702.1

Commits

• See full diff in compare view

Updates @vitejs/plugin-react from 6.0.2 to 6.0.3

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.0.3 (2026-06-23)

Commits

• 640fd35 release: plugin-react@6.0.3
• 889efb0 fix(deps): update all non-major dependencies (#1249)
• 6c57dd4 fix(plugin-react): use '/' base in bundledDev preamble to fix non-root base p...
• 3cc33a7 fix(deps): update react-related dependencies (#1245)
• c0f7c7f docs: mention the Biome rule in the "Consistent components exports" section (...
• cd80f0f fix(deps): update all non-major dependencies (#1241)
• e38acca fix(deps): update all non-major dependencies (#1227)
• 9a9bb26 perf(react): improve react compiler preset so that slightly more modules are ...
• See full diff in compare view

Updates vite from 8.0.16 to 8.1.3

Release notes

Sourced from vite's releases.

v8.1.3

Please refer to CHANGELOG.md for details.

v8.1.2

Please refer to CHANGELOG.md for details.

v8.1.1

Please refer to CHANGELOG.md for details.

create-vite@8.1.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.1.0

Please refer to CHANGELOG.md for details.

v8.1.0

Please refer to CHANGELOG.md for details.

plugin-legacy@8.1.0-beta.0

Please refer to CHANGELOG.md for details.

v8.1.0-beta.0

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

8.1.3 (2026-07-02)

Bug Fixes

• css: inject inlined CSS after the shebang line (#22717) (1534d36)
• deps: bump es-module-lexer to 2.3.0 (#22838) (7103c3a)
• preload css for nested dynamic imports (#22759) (2c53054)
• ssr: correct stacktrace column position for first line (#22828) (c4acd69)

8.1.2 (2026-06-30)

Bug Fixes

• deps: revert es-module-lexer to 2.1.0 (#22827) (0d3bd7c)
• restore, "fix: resolve pnpm .modules.yaml from workspace root instead of cwd (#22757)" (#22825) (efb98cc)
• revert, "fix: escape ids with multiple null bytes (#22687)" (cccef55)
• revert, "fix: resolve pnpm .modules.yaml from workspace root instead of cwd (#22757)" (cf97711)

8.1.1 (2026-06-30)

Features

• update dynamic import warning to link to Vite docs (#22823) (62bd7af)

Bug Fixes

• bundled-dev: avoid stack overflow on import.meta.hot.invalidate() (#22797) (709eb8e)
• bundled-dev: serve assets emitted during HMR/lazy compile (#22745) (5876b2c)
• bundledDev: skip plugin transform hooks for rolldown-lazy stub modules (#22778) (8f925e2)
• css: preserve dollar signs in external @import urls with lightningcss (#22718) (9fa7ab4)
• css: resolve tsconfig paths in CSS and Sass @​import (#22775) (ef0b891)
• deps: update all non-major dependencies (#22734) (e635f49)
• deps: update all non-major dependencies (#22804) (8837400)
• deps: update rolldown-related dependencies (#22591) (2ce6677)
• escape ids with multiple null bytes (#22687) (833fc30)
• hide console window when running 'net use' on Windows (#22698) (92b63f2)
• ignore bundled config temp dir (#22800) (043a810)
• invert esbuild.jsxSideEffects when converting to oxc.jsx.pure (#22809) (33895ba)
• optimize-deps: ignore ERR_CLOSED_SERVER in scanner (#22784) (085a0ab)
• optimizer: scanner should resolve input from root (#22769) (9722b07)
• resolve pnpm .modules.yaml from workspace root instead of cwd (#22757) (2531ac7)
• return sourcemap field from some plugins that were lacking (#22782) (7e18bf8)
• server: handle malformed URI in indexHtmlMiddleware (#22781) (84f5ccc)

Miscellaneous Chores

• improve dependency optimizer messages (#22549) (092cb3b)

Code Refactoring

• css: remove lightningcss null byte bug workaround (#22822) (2dafd3b)
• use pre-defined environments variable to avoid duplicate Object.values calls (#22790) (1113acf)

... (truncated)

Commits

• 578ffb8 release: v8.1.3
• 7103c3a fix(deps): bump es-module-lexer to 2.3.0 (#22838)
• 1534d36 fix(css): inject inlined CSS after the shebang line (#22717)
• c4acd69 fix(ssr): correct stacktrace column position for first line (#22828)
• 2c53054 fix: preload css for nested dynamic imports (#22759)
• ba31193 release: v8.1.2
• 0d3bd7c fix(deps): revert es-module-lexer to 2.1.0 (#22827)
• efb98cc fix: restore, "fix: resolve pnpm .modules.yaml from workspace root instead of...
• cf97711 fix: revert, "fix: resolve pnpm .modules.yaml from workspace root instead of ...
• cccef55 fix: revert, "fix: escape ids with multiple null bytes (#22687)"
• Additional commits viewable in compare view

Updates wrangler from 4.102.0 to 4.107.0

Release notes

Sourced from wrangler's releases.

wrangler@4.107.0

Minor Changes

• #14474 aa5d580 Thanks @​WillTaylorDev! - Add cache options for WorkerEntrypoint exports

  You can now set cache options on WorkerEntrypoint exports and configure cross-version cache behavior globally:

  // wrangler.json
  {
    "cache": { "enabled": true, "cross_version_cache": true },
    "exports": {
      "default": {
        "type": "worker",
        "cache": { "enabled": false }
      },
      "Admin": {
        "type": "worker",
        "cache": { "enabled": true }
      }
    }
  }

  Wrangler sends the exports config to the deploy and version upload APIs alongside the global cache.enabled and cache.cross_version_cache settings. The platform resolves those global settings plus cache overrides on exports and validates which entrypoint names are cacheable.

• #14382 fd92d56 Thanks @​petebacondarwin! - Add support for declarative Durable Object exports

  wrangler deploy now accepts an exports map in wrangler.json as a declarative alternative to the legacy migrations array.

  Each entry in exports is keyed by Durable Object class name. type carries the export kind (currently always "durable-object"); the state field carries the lifecycle and defaults to "created" (live) when omitted:

  {
    "exports": {
      // Provision a new Durable Object class (`MyDO`)
      "MyDO": { "type": "durable-object", "storage": "sqlite" },
      // Delete Durable Object class (`OldGone`)
      "OldGone": { "type": "durable-object", "state": "deleted" },
      // Rename a Durable Object class (from `OldName` to `NewName`)
      "OldName": {
        "type": "durable-object",
        "state": "renamed",
        "renamed_to": "NewName"
      },
      "NewName": { "type": "durable-object", "storage": "sqlite" },
      // Transfer a Durable Object (`Outgoing`) to a new Worker (`target-worker`)
      "Outgoing": {
        "type": "durable-object",
        "state": "transferred",

... (truncated)

Commits

• 473e61f Version Packages (#14503)
• c8dbcf5 [wrangler] Remove experimental gate for declarative Durable Object exports (#...
• 98793d8 [wrangler] Improve asset upload performance with single-file uploads (#14305)
• be3f792 [wrangler] Add wrangler flagship commands (#14423)
• e1532eb [wrangler] Add opt-in OS keychain storage for OAuth credentials (#14156)
• aa5d580 WC-5321 Add cache options for WorkerEntrypoint exports (#14474)
• fd92d56 [wrangler] Add experimental support for declarative Durable Object exports (#...
• 0277bfa Improve error message when deploying to a non-existent Pages project in non-i...
• bfe48db [wrangler] fix: remove stale --experimental-vm-modules flag and prevent silen...
• 6b0ce98 Bump the workerd-and-workers-types group with 2 updates (#14502)
• 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