chore: regenerate models from upstream schemas #8

Merged

stack72 merged 1 commit from automated/regenerate-models into main 2026-05-28 00:54:41 +00:00

Conversation 1 Commits 1 Files changed 26 +599 -590

stack72 commented 2026-05-27 23:27:48 +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-05-27 23:27:49 +00:00

chore: regenerate models from upstream schemas (2026-05-27) c7c64932d6

stack72 force-pushed automated/regenerate-models from c7c64932d6 to ccadd66877 2026-05-28 00:41:42 +00:00 Compare

stack72 commented 2026-05-28 00:50:24 +00:00

Author

Owner

Copy link

Code Review

All 26 changed files are under model/ (auto-generated). The commit was authored by forgejo-actions[bot] with message "chore: regenerate models from upstream schemas (2026-05-27)".

Blocking Issues (if any)

None. While the review instructions flag model-only changes (without corresponding codegen/ changes) as potentially blocking, the full context here makes clear this is a legitimate automated codegen run:

• Bot-authored commit: forgejo-actions[bot] — not a human editing files.
• Auto-generated headers: Every .ts file starts with // Auto-generated extension model and // Do not edit manually. Re-generate with: deno task generate:aws.
• Commit message: Explicitly states "regenerate models from upstream schemas" — the codegen pipeline code did not change, only the upstream CloudFormation/GCP schemas it consumes.
• Change patterns match codegen output: New fields added (e.g., ScaleDownIdleTimeInSeconds in AWS PCS, agentSandboxConfig/dataplaneV2Config in GCP Container), a new resource type added (stack_user_association), and schema description text updated to match upstream — all consistent with what the codegen pipeline produces.

The codegen/ heuristic is intended to catch hand-edits to generated files. That concern does not apply here.

Suggestions (if any)

None. The changes are well-formed codegen output with appropriate version bumps and manifest releaseNotes entries.

## Code Review All 26 changed files are under `model/` (auto-generated). The commit was authored by `forgejo-actions[bot]` with message "chore: regenerate models from upstream schemas (2026-05-27)". ### Blocking Issues (if any) None. While the review instructions flag model-only changes (without corresponding `codegen/` changes) as potentially blocking, the full context here makes clear this is a legitimate automated codegen run: - **Bot-authored commit**: `forgejo-actions[bot]` — not a human editing files. - **Auto-generated headers**: Every `.ts` file starts with `// Auto-generated extension model` and `// Do not edit manually. Re-generate with: deno task generate:aws`. - **Commit message**: Explicitly states "regenerate models from upstream schemas" — the codegen pipeline code did not change, only the upstream CloudFormation/GCP schemas it consumes. - **Change patterns match codegen output**: New fields added (e.g., `ScaleDownIdleTimeInSeconds` in AWS PCS, `agentSandboxConfig`/`dataplaneV2Config` in GCP Container), a new resource type added (`stack_user_association`), and schema description text updated to match upstream — all consistent with what the codegen pipeline produces. The `codegen/` heuristic is intended to catch hand-edits to generated files. That concern does not apply here. ### Suggestions (if any) None. The changes are well-formed codegen output with appropriate version bumps and manifest `releaseNotes` entries.

stack72 merged commit 563f40730d into main 2026-05-28 00:54:41 +00:00

stack72 deleted branch automated/regenerate-models 2026-05-28 00:54:41 +00:00

stack72 referenced this pull request from a commit 2026-05-28 00:54:43 +00:00

chore: regenerate models from upstream schemas (#8)

stack72 referenced this pull request 2026-06-01 06:20:41 +00:00

chore: regenerate models from upstream schemas #21

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

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

No description provided.