chore: regenerate models from upstream schemas #48

Merged

stack72 merged 1 commit from automated/regenerate-models into main 2026-06-10 13:08:38 +00:00

Conversation 1 Commits 1 Files changed 16 +294 -150

stack72 commented 2026-06-10 06:11:21 +00:00

Owner

Copy link

Summary

Automated regeneration of extension models from upstream provider schemas.

Schema Sources

• AWS: CloudFormation Resource Schema
• GCP: Google Discovery Documents
• Hetzner: Hetzner Cloud OpenAPI spec
• DigitalOcean: DigitalOcean OpenAPI spec

Review Notes

• Files under model/ are auto-generated — review the manifest.yaml diffs for version changes
• CalVer versioning with content-based change detection ensures versions only bump when content changes
• Publishing happens automatically when this PR is merged (via the publish workflow)

## Summary Automated regeneration of extension models from upstream provider schemas. ### Schema Sources - **AWS**: CloudFormation Resource Schema - **GCP**: Google Discovery Documents - **Hetzner**: Hetzner Cloud OpenAPI spec - **DigitalOcean**: DigitalOcean OpenAPI spec ### Review Notes - Files under `model/` are auto-generated — review the `manifest.yaml` diffs for version changes - CalVer versioning with content-based change detection ensures versions only bump when content changes - Publishing happens automatically when this PR is merged (via the publish workflow)

stack72 added 1 commit 2026-06-10 06:11:21 +00:00

chore: regenerate models from upstream schemas (2026-06-10) 18adf8d515

stack72 commented 2026-06-10 06:24:21 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Observations

All 16 changed files are auto-generated files under model/ — per CLAUDE.md, their content is not reviewed. The nature of the changes was verified against the two-case rule for model-only PRs:

• All manifest files show a consistent version bump from 2026.06.08.2 → 2026.06.10.1, with correct Updated: entries listing only the affected models.
• All .ts model files contain the matching version bump, a new upgrade entry, and upstream-schema-driven changes (new fields, new sub-schemas, field reordering). These are consistent with re-running the existing codegen pipeline against updated upstream schemas, not hand-editing.
• No codegen/ changes are present because the generation pipeline itself was not modified — only the upstream schema inputs changed.

The commit message ("chore: regenerate models from upstream schemas") and diff pattern match the established regeneration workflow seen in prior PRs (e.g., #47). No evidence of hand-editing was found.

## Code Review ### Blocking Issues None. ### Observations All 16 changed files are auto-generated files under `model/` — per CLAUDE.md, their content is not reviewed. The nature of the changes was verified against the two-case rule for model-only PRs: - **All manifest files** show a consistent version bump from `2026.06.08.2` → `2026.06.10.1`, with correct `Updated:` entries listing only the affected models. - **All `.ts` model files** contain the matching version bump, a new upgrade entry, and upstream-schema-driven changes (new fields, new sub-schemas, field reordering). These are consistent with re-running the existing codegen pipeline against updated upstream schemas, not hand-editing. - **No `codegen/` changes** are present because the generation pipeline itself was not modified — only the upstream schema inputs changed. The commit message ("chore: regenerate models from upstream schemas") and diff pattern match the established regeneration workflow seen in prior PRs (e.g., `#47`). No evidence of hand-editing was found.

stack72 merged commit f9ee1b766d into main 2026-06-10 13:08:38 +00:00

stack72 deleted branch automated/regenerate-models 2026-06-10 13:08:39 +00:00

stack72 referenced this pull request from a commit 2026-06-10 13:08:39 +00:00

chore: regenerate models from upstream schemas (#48)

stack72 referenced this pull request 2026-06-12 06:24:24 +00:00

chore: regenerate models from upstream schemas #51

stack72 referenced this pull request 2026-06-16 06:23:32 +00:00

chore: regenerate models from upstream schemas #55

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

No description provided.