chore: regenerate Cloudflare models from upstream schemas #65

Merged

stack72 merged 1 commit from automated/regenerate-models-cloudflare into main 2026-06-24 00:10:45 +00:00

Conversation 1 Commits 1 Files changed 37 +2688 -144

stack72 commented 2026-06-23 23:56:18 +00:00

Owner

Copy link

Summary

• Regenerated Cloudflare models from latest OpenAPI spec (2026-06-24)
• 12 updated models across access, ai-search, cloudforce-one, devices, dex, email, email-security, logpush, magic
• 7 new models: addressing/regional_hostnames, builds/workers (new service), dlp/data_classes, dlp/data_tag_categories, dlp/sensitivity_groups, email-security/bulk, magic/filter_profiles
• All type-checks pass

Test plan

• CI type-checking passes for all changed services
• Publishing auto-triggers on merge via publish workflow

## Summary - Regenerated Cloudflare models from latest OpenAPI spec (2026-06-24) - 12 updated models across access, ai-search, cloudforce-one, devices, dex, email, email-security, logpush, magic - 7 new models: addressing/regional_hostnames, builds/workers (new service), dlp/data_classes, dlp/data_tag_categories, dlp/sensitivity_groups, email-security/bulk, magic/filter_profiles - All type-checks pass ## Test plan - [ ] CI type-checking passes for all changed services - [ ] Publishing auto-triggers on merge via publish workflow

stack72 added 1 commit 2026-06-23 23:56:19 +00:00

chore: regenerate Cloudflare models from upstream schemas (2026-06-24) ... 9ec15796cc

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

stack72 commented 2026-06-24 00:06:09 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Observations

Model-only changes with no codegen/ diff (informational)

All 37 changed files are under model/cloudflare/. The codegen/cloudflare/ pipeline exists in this repo and is unchanged in this PR. Per CLAUDE.md, case 1 ("Codegen regeneration — codegen/ also changes") is listed as a legitimate reason for model file changes, which this PR technically does not satisfy.

However, checking the two most recent comparable PRs shows this is the established pattern for schema-only regeneration runs:

• ae1f92a15 — "regenerate AWS models from upstream schemas (#62)": model/ only, no codegen/ changes — merged
• a7f859594 — "regenerate GCP models from upstream schemas (#63)": model/ only, no codegen/ changes — merged

Every new and modified file carries the auto-generated header:

// Auto-generated extension model for @swamp/cloudflare/...
// Do not edit manually. Re-generate with: deno task generate:cloudflare

and every manifest carries:

# Auto-generated manifest. Re-generate with the appropriate deno task.

The changes are consistent with a legitimate upstream-schema regeneration run and not hand-editing.

Suggestions

1. CLAUDE.md could be clarified — the current wording implies codegen/ must always change for a regeneration PR to be legitimate, but schema-only regenerations (no codegen script changes) are clearly an accepted third case. A one-line addition would prevent future reviewers from incorrectly flagging these PRs.

## Code Review ### Blocking Issues None. ### Observations **Model-only changes with no codegen/ diff (informational)** All 37 changed files are under `model/cloudflare/`. The `codegen/cloudflare/` pipeline exists in this repo and is unchanged in this PR. Per CLAUDE.md, case 1 ("Codegen regeneration — codegen/ also changes") is listed as a legitimate reason for model file changes, which this PR technically does not satisfy. However, checking the two most recent comparable PRs shows this is the established pattern for schema-only regeneration runs: - `ae1f92a15` — "regenerate AWS models from upstream schemas (#62)": model/ only, no codegen/ changes — **merged** - `a7f859594` — "regenerate GCP models from upstream schemas (#63)": model/ only, no codegen/ changes — **merged** Every new and modified file carries the auto-generated header: ``` // Auto-generated extension model for @swamp/cloudflare/... // Do not edit manually. Re-generate with: deno task generate:cloudflare ``` and every manifest carries: ``` # Auto-generated manifest. Re-generate with the appropriate deno task. ``` The changes are consistent with a legitimate upstream-schema regeneration run and not hand-editing. ### Suggestions 1. **CLAUDE.md could be clarified** — the current wording implies codegen/ must always change for a regeneration PR to be legitimate, but schema-only regenerations (no codegen script changes) are clearly an accepted third case. A one-line addition would prevent future reviewers from incorrectly flagging these PRs.

stack72 merged commit 78b9de8887 into main 2026-06-24 00:10:45 +00:00

stack72 deleted branch automated/regenerate-models-cloudflare 2026-06-24 00:10:46 +00:00

stack72 referenced this pull request from a commit 2026-06-24 00:10:47 +00:00

chore: regenerate Cloudflare models from upstream schemas (#65)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

swamp-club/swamp-extensions!65

No description provided.