build(deps-dev): bump wrangler from 4.87.0 to 4.88.0 in /cornucopia.owasp.org

[dependabot]

Bumps wrangler from 4.87.0 to 4.88.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.88.0

Minor Changes

• #13760 e07825a Thanks @​danielgek! - Add builtin storage option to wrangler ai-search create.

  wrangler ai-search create now supports a third storage type, builtin, in addition to r2 and web-crawler. When --type builtin is selected (or chosen interactively), Wrangler creates the instance using Cloudflare-managed storage by omitting type and source from the API request — the API treats an absent type as builtin storage. Builtin instances do not accept --source, --prefix, --include-items, or --exclude-items.

• #13721 58899d8 Thanks @​danielgek! - Add optional custom_metadata step to wrangler ai-search create

  The wrangler ai-search create interactive wizard now lets you declare custom metadata fields that the new AI Search instance should index. Each field is a field_name paired with a data_type (text, number, boolean, or datetime).

  You can provide fields up-front via the new repeatable --custom-metadata flag using field_name:data_type syntax:

  wrangler ai-search create my-instance \
    --type r2 --source my-bucket \
    --custom-metadata title:text \
    --custom-metadata views:number

  For larger schemas, use --custom-metadata-schema to point at a JSON file containing an array of { field_name, data_type } objects:

  wrangler ai-search create my-instance \
    --type r2 --source my-bucket \
    --custom-metadata-schema schema.json

  [
    { "field_name": "title", "data_type": "text" },
    { "field_name": "views", "data_type": "number" }
  ]

• #13701 18b9d5b Thanks @​dario-piotrowicz! - Prompt for missing name and compatibility date interactively during wrangler deploy

  When deploying without a project name or compatibility_date in your configuration or CLI arguments, wrangler deploy now interactively prompts for the missing values instead of immediately failing with an error. For compatibility date, the prompt offers to use today's date; if you decline, the existing error is shown. The compatibility date prompt is skipped when --latest is passed. In non-interactive or CI environments, behavior is unchanged.

  Additionally, when no config file exists, wrangler deploy now offers to save the prompted name and compatibility date to a wrangler.jsonc file for future use. This interactive flow is available for all wrangler deploy invocations — not just asset-only deployments.

• #13810 2b8c0cc Thanks @​jamesopstad! - Stabilize the secrets configuration property

  The secrets property in the Wrangler config file is no longer experimental and will no longer emit an experimental warning when used. Required secrets are validated during local development and deploy, and used as the source of truth for type generation.

  {
    "secrets": {
      "required": ["API_KEY", "DB_PASSWORD"]
    }

... (truncated)

Commits

• 0605474 Version Packages (#13766)
• 9f532f7 fix(wrangler): support Flagship bindings with wrangler preview (#13818)
• 3ceadef fix(wrangler): skip versions deploy prompts for args (#13739)
• e07825a feat(wrangler): add built in storage to AI Search (#13760)
• 25f5ef2 increase test coverage for deploy and versions upload in preparation for refa...
• 18b9d5b Prompt for missing name and compatibility date interactively during `wrangler...
• 0099265 Bump the workerd-and-workers-types group with 2 updates (#13800)
• 58899d8 feat(wrangler): add custom metadata to instance creation on ai search (#13721)
• 1127114 [wrangler] Remove redundant dev-registry filtering (#12974)
• 1a5cc86 fix(wrangler): preserve request ports with --host flag (#13745)
• Additional commits viewable in compare view

[sydseter]

@dependabot rebase

[sydseter]

@dependabot rebase