GeezerVison

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 6, 2026 10:45pm

PR Summary

Medium Risk
Changes affect live Cloudflare API calls for DNS listing filters and zone-setting updates (including SSL/TLS-related settings), where incorrect coercion previously caused API rejections; removals (jump_start, minify) only drop dead options against the current API.

Overview
Aligns the Cloudflare block, tools, docs, and integration catalog with the current Cloudflare API and fixes request-building bugs that could cause failed or incorrect API calls.

cloudflare_update_zone_setting no longer runs JSON.parse on every value. It passes through object/array values from block references, coerces browser_cache_ttl to a number, and only parses JSON when the input looks like {...} or [...] so scalars like min_tls_version: "1.2" stay strings.

cloudflare_list_dns_records now sends name.exact, content.exact, and tag.exact (and keeps comment.contains) instead of bare query keys that did not match the API’s filter semantics.

Create zone drops the unsupported jump_start field from the tool, types, block UI, and param mapping. List zones gains plan.id sort in the block and tool docs. Create zone adds secondary as a zone type in the block.

Update zone setting UI and copy remove deprecated/invalid minify / auto_minify options; wand prompts and docs are updated accordingly. DNS tag filtering is documented and labeled as a single exact tag name.

Two new BlockMeta skills cover zone provisioning and SPF/DKIM/DMARC setup. integrations.json descriptions and updatedAt are refreshed to match.

^{Reviewed by Cursor Bugbot for commit f3f3596. Configure here.}

@greptile review

@cursor review

Greptile Summary

This PR aligns the Cloudflare integration with the live API by fixing a real type-coercion bug in update_zone_setting, switching DNS record filters to Cloudflare's exact-match dotted parameters (name.exact, content.exact, tag.exact), removing deprecated and non-existent settings (minify, auto_minify, jump_start), and expanding the block UI with missing options (secondary zone type, plan.id sort).

• Type-coercion fix (update_zone_setting.ts): The previous implementation blindly JSON.parse'd every value, silently converting scalar settings like min_tls_version: "1.2" to the number 1.2, which the Cloudflare API rejects. The new code only JSON-parses values that begin with { or [, and special-cases browser_cache_ttl for numeric coercion.
• DNS filter alignment (list_dns_records.ts): name, content, and tag filters now use Cloudflare's exact-match query-param form (name.exact, content.exact, tag.exact) instead of the bare params that the API does not honour in the same way.
• Cleanup: Removed jump_start from create_zone (not in current POST /zones schema), dropped deprecated minify/auto_minify from the settings dropdown, and updated descriptions, docs, and templates accordingly.

Confidence Score: 5/5

Safe to merge — all changes are targeted API-alignment fixes with no new logic paths that could cause regressions on currently-working settings.

The body-builder rewrite in update_zone_setting.ts is the only non-trivial logic change, and it correctly handles every runtime type that can flow through the param. The DNS filter changes swap bare params for Cloudflare's documented exact-match equivalents. Removed fields were already broken against the live API. No currently-working code path is regressed.

No files require special attention. update_zone_setting.ts received the most logic change and is well-commented.

Important Files Changed

_{Reviews (7): Last reviewed commit: "revert(cloudflare): keep original block ..." | Re-trigger Greptile}

Greptile Summary

This PR aligns the Cloudflare integration with the live API by fixing a type-coercion bug, correcting DNS record filter params, and removing stale/deprecated fields and settings.

• update_zone_setting: Replaces the blanket JSON.parse with a targeted dispatch — browser_cache_ttl is explicitly coerced to an integer, JSON object/array literals (e.g. ciphers) are parsed, and all other scalar settings stay as strings, preventing the previous silent coercion of "1.2" → 1.2 that caused API rejections.
• list_dns_records: name, content, and tag query params are renamed to their dotted exact-match equivalents (name.exact, content.exact, tag.exact) as the Cloudflare v4 API requires for deterministic filtering.
• Deprecations removed: jump_start (no longer in the POST /zones schema), minify and auto_minify (removed from the zone-settings API in Aug 2024) are dropped from params, types, the block dropdown, and docs; secondary zone type and plan.id sort field are added.

Confidence Score: 4/5

Safe to merge; all changes are API-alignment fixes and deprecation removals with no core path regressions.

The update_zone_setting body builder is materially improved — the previous blind JSON.parse coerced "1.2" to 1.2 and broke the Cloudflare API; the new dispatch is correct for every setting in the exposed dropdown. The trimmed variable is computed but the three fallback return paths use params.value instead, meaning whitespace-padded inputs for string settings (e.g. " on ") are sent unstripped to the API. This is a pre-existing quirk carried over from the old catch block, but since trimmed is now available it should be used consistently. The remaining changes (DNS exact-match params, deprecated field removal, brand color, new zone type, sort option) are straightforward and well-documented.

apps/sim/tools/cloudflare/update_zone_setting.ts — the trimmed/params.value inconsistency in the fallback returns warrants a look before merge.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[update_zone_setting called] --> B[trimmed = params.value.trim]
    B --> C{settingId is browser_cache_ttl?}
    C -->|Yes| D[numeric = Number of trimmed]
    D --> E{isNaN?}
    E -->|Yes| F[send string fallback]
    E -->|No| G[send as integer]
    C -->|No| H{trimmed starts with curly or bracket?}
    H -->|Yes - JSON literal| I[JSON.parse trimmed]
    I --> J{Parse OK?}
    J -->|Yes| K[send as parsed object or array]
    J -->|No| L[send string fallback]
    H -->|No - plain scalar| M[send as string e.g. full or on or 1.2]
    G --> N[PATCH /zones/:id/settings/:settingId]
    K --> N
    M --> N
    F --> N
    L --> N

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[update_zone_setting called] --> B[trimmed = params.value.trim]
    B --> C{settingId is browser_cache_ttl?}
    C -->|Yes| D[numeric = Number of trimmed]
    D --> E{isNaN?}
    E -->|Yes| F[send string fallback]
    E -->|No| G[send as integer]
    C -->|No| H{trimmed starts with curly or bracket?}
    H -->|Yes - JSON literal| I[JSON.parse trimmed]
    I --> J{Parse OK?}
    J -->|Yes| K[send as parsed object or array]
    J -->|No| L[send string fallback]
    H -->|No - plain scalar| M[send as string e.g. full or on or 1.2]
    G --> N[PATCH /zones/:id/settings/:settingId]
    K --> N
    M --> N
    F --> N
    L --> N

_{Reviews (2): Last reviewed commit: "fix(cloudflare): reject empty browser_ca..." | Re-trigger Greptile}

Addressed the tag_match/tag.exact semantics note from the Greptile summary (Comments Outside Diff) in 493cb56 — updated the tag_match param description to document that it only affects results when combined with multiple tag filter conditions and has no effect with the single exact-match Tag Filter. Verified against Cloudflare's live DNS records list API docs: tag.exact matches a single name:value pair, so exposing multiple simultaneous tag conditions (present/absent/exact/startswith/etc.) would be a larger feature addition out of scope for this alignment/bug-fix pass.

@greptile review

@cursor review

@greptile review

@greptile review

@cursor review

@greptile review

@cursor review

@greptile review

@cursor review