chore: regenerate models from upstream schemas #24

Merged

stack72 merged 1 commit from automated/regenerate-models into main 2026-06-03 12:51:45 +00:00

Conversation 1 Commits 1 Files changed 57 +3536 -706

stack72 commented 2026-06-02 06:08:25 +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-02 06:08:25 +00:00

chore: regenerate models from upstream schemas (2026-06-02) f849e60de3

stack72 force-pushed automated/regenerate-models from f849e60de3 to e0e1ac8756 2026-06-03 06:08:52 +00:00 Compare

stack72 commented 2026-06-03 06:20:36 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Observations

This is a scheduled "regenerate models from upstream schemas" PR (Forgejo Actions bot commit). All changed files are under model/ — the codegen pipeline was run against updated upstream schemas; the pipeline source itself (codegen/) did not need to change because only the provider schemas changed, not the generation logic. This is the third legitimate pattern beyond the two listed in CLAUDE.md (pipeline-source change + regen, and version-bump-only). All files carry the standard auto-generated banner and follow the repo's conventions.

Verified for the changed files:

• Auto-generated banners present on all .ts model files (// Auto-generated extension model for … Do not edit manually.) and all manifest.yaml files (# Auto-generated manifest. Re-generate with the appropriate deno task.).
• New module model/aws/resiliencehubv2/: deno.lock is committed ✓; deno.json pins all three dependencies to exact versions (zod@4.3.6, @aws-sdk/client-cloudcontrol@3.1021.0, fast-json-patch@3.1.1) ✓; model files use export const model = { … } (named export, no default export) ✓.
• any types: only in generated code, gated by // deno-lint-ignore-file no-explicit-any ✓.
• Security: no hardcoded credentials; instance-name sanitisation pattern (.replace(/[\/\\]/g, "_").replace(/\.\./g, "_").replace(/\0/g, "")) prevents path-traversal ✓.
• Version format: all manifests use CalVer 2026.06.03.1 ✓.
• Release notes: each manifest accurately describes which resource types were Added or Updated ✓.

Suggestions

None.

## Code Review ### Blocking Issues None. ### Observations This is a scheduled "regenerate models from upstream schemas" PR (Forgejo Actions bot commit). All changed files are under `model/` — the codegen pipeline was run against updated upstream schemas; the pipeline source itself (`codegen/`) did not need to change because only the provider schemas changed, not the generation logic. This is the third legitimate pattern beyond the two listed in CLAUDE.md (pipeline-source change + regen, and version-bump-only). All files carry the standard auto-generated banner and follow the repo's conventions. Verified for the changed files: - **Auto-generated banners present** on all `.ts` model files (`// Auto-generated extension model for … Do not edit manually.`) and all `manifest.yaml` files (`# Auto-generated manifest. Re-generate with the appropriate deno task.`). - **New module `model/aws/resiliencehubv2/`**: `deno.lock` is committed ✓; `deno.json` pins all three dependencies to exact versions (`zod@4.3.6`, `@aws-sdk/client-cloudcontrol@3.1021.0`, `fast-json-patch@3.1.1`) ✓; model files use `export const model = { … }` (named export, no default export) ✓. - **`any` types**: only in generated code, gated by `// deno-lint-ignore-file no-explicit-any` ✓. - **Security**: no hardcoded credentials; instance-name sanitisation pattern (`.replace(/[\/\\]/g, "_").replace(/\.\./g, "_").replace(/\0/g, "")`) prevents path-traversal ✓. - **Version format**: all manifests use CalVer `2026.06.03.1` ✓. - **Release notes**: each manifest accurately describes which resource types were Added or Updated ✓. ### Suggestions None.

stack72 merged commit a8676ee928 into main 2026-06-03 12:51:45 +00:00

stack72 referenced this pull request from a commit 2026-06-03 12:51:47 +00:00

chore: regenerate models from upstream schemas (#24)

stack72 deleted branch automated/regenerate-models 2026-06-03 12:51:51 +00:00

stack72 referenced this pull request 2026-06-03 13:02:52 +00:00

feat(issue-lifecycle): add platform type to IssueType Zod schema #27

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

No description provided.