chore: regenerate GCP models from upstream schemas #63

Merged

stack72 merged 1 commit from automated/regenerate-models-gcp into main 2026-06-23 23:29:34 +00:00

Conversation 1 Commits 1 Files changed 77 +2211 -572

stack72 commented 2026-06-23 23:15:35 +00:00

Owner

Copy link

Summary

• Regenerated GCP models from latest Google Discovery Documents (2026-06-24)
• 52 changed models across 25 services
• 3 new models: gkehub/rollouts, gkehub/rolloutsequences, gmailpostmastertools/domains_users
• 2 removed orphan models: saasservicemgmt/saasreleases, saasservicemgmt/unitgroups
• All version and upgrade stanza consistency verified

Changed services

apigee, assuredworkloads, bigquery, compute, config, contactcenterinsights, container, datapipelines, dataproc, developerconnect, discoveryengine, eventarc, gkehub, gmailpostmastertools, monitoring, networkconnectivity, networkmanagement, ondemandscanning, pubsub, redis, saasservicemgmt, securesourcemanager, securitycenter, securityposture, youtube

Test plan

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

## Summary - Regenerated GCP models from latest Google Discovery Documents (2026-06-24) - 52 changed models across 25 services - 3 new models: gkehub/rollouts, gkehub/rolloutsequences, gmailpostmastertools/domains_users - 2 removed orphan models: saasservicemgmt/saasreleases, saasservicemgmt/unitgroups - All version and upgrade stanza consistency verified ## Changed services apigee, assuredworkloads, bigquery, compute, config, contactcenterinsights, container, datapipelines, dataproc, developerconnect, discoveryengine, eventarc, gkehub, gmailpostmastertools, monitoring, networkconnectivity, networkmanagement, ondemandscanning, pubsub, redis, saasservicemgmt, securesourcemanager, securitycenter, securityposture, youtube ## 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:15:35 +00:00

chore: regenerate AWS models from upstream schemas (2026-06-23) ... 9fa1ed3998

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

stack72 force-pushed automated/regenerate-models-gcp from 8a363b8ad7 to 8866d8c11b 2026-06-23 23:16:28 +00:00 Compare

stack72 commented 2026-06-23 23:27:12 +00:00

Author

Owner

Copy link

Code Review

Blocking Issues

None.

Suggestions

None.

---

All 77 changed files are auto-generated GCP model files under model/gcp/. The commit message ("chore: regenerate GCP models from upstream schemas (2026-06-24)") and the file contents confirm this is a legitimate codegen regeneration run against updated upstream GCP schemas — not hand-editing.

Key observations:

• Every modified .ts file carries the standard auto-generated header and "Do not edit manually. Re-generate with: deno task generate:gcp" notice.
• No codegen/ pipeline files changed, consistent with a schema-only upstream update (pipeline logic unchanged, schemas evolved).
• This matches the exact pattern of recent merges to main: ae1f92a15 chore: regenerate AWS models from upstream schemas, aeb7369fd chore: regenerate models from upstream schemas, etc.
• Manifest changes are well-formed: version bumped to 2026.06.24.x, releaseNotes updated with accurate added/updated entries, new model files listed in the models array (rolloutsequences.ts, domains_users.ts).
• New resource additions (e.g. gkehub/rolloutsequences, gmailpostmastertools/domains_users) and content updates (e.g. apigee/apiproducts gaining payloadOperationGroup) are consistent with upstream GCP API schema evolution.

No hand-editing, no security issues, no correctness concerns. Ready to merge.

## Code Review ### Blocking Issues None. ### Suggestions None. --- All 77 changed files are auto-generated GCP model files under `model/gcp/`. The commit message ("chore: regenerate GCP models from upstream schemas (2026-06-24)") and the file contents confirm this is a legitimate codegen regeneration run against updated upstream GCP schemas — not hand-editing. Key observations: - Every modified `.ts` file carries the standard auto-generated header and "Do not edit manually. Re-generate with: `deno task generate:gcp`" notice. - No `codegen/` pipeline files changed, consistent with a schema-only upstream update (pipeline logic unchanged, schemas evolved). - This matches the exact pattern of recent merges to main: `ae1f92a15 chore: regenerate AWS models from upstream schemas`, `aeb7369fd chore: regenerate models from upstream schemas`, etc. - Manifest changes are well-formed: version bumped to `2026.06.24.x`, `releaseNotes` updated with accurate added/updated entries, new model files listed in the `models` array (`rolloutsequences.ts`, `domains_users.ts`). - New resource additions (e.g. `gkehub/rolloutsequences`, `gmailpostmastertools/domains_users`) and content updates (e.g. `apigee/apiproducts` gaining `payloadOperationGroup`) are consistent with upstream GCP API schema evolution. No hand-editing, no security issues, no correctness concerns. Ready to merge.

stack72 merged commit a7f8595940 into main 2026-06-23 23:29:34 +00:00

stack72 deleted branch automated/regenerate-models-gcp 2026-06-23 23:29:35 +00:00

stack72 referenced this pull request from a commit 2026-06-23 23:29:36 +00:00

chore: regenerate GCP models from upstream schemas (#63)

stack72 referenced this pull request 2026-06-24 00:06:09 +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!63

No description provided.