chore(codegen): daily schema refresh (2026-06-12) - #34
Open
timgl wants to merge 1 commit into
Open
Conversation
Regenerate src/generated/api.d.ts from the live PostHog OpenAPI spec via `pnpm codegen`. The filter (openapi-filter.yaml) is unchanged — this cycle is pure schema drift on already-managed operations (+1634/-115 lines). The live spec renamed the dashboards_partial_update request body component `PatchedDashboard` → `PatchedPatchedDashboardOpenApi`. Update the type alias in src/resources/dashboard/client.ts to match; no behavior change. typecheck and test pass. Generated-By: PostHog Code Task-Id: e4980cc3-e437-4d44-888f-d164247f4034
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Daily OpenAPI schema refresh — 2026-06-12
Automated regeneration of
src/generated/api.d.tsfrom the live PostHog OpenAPIspec (
https://us.posthog.com/api/schema/?format=json, filtered byopenapi-filter.yaml). Generated viapnpm codegen—api.d.tswas nothand-edited.
Spec diff size
src/generated/api.d.tsopenapi-filter.yamlThis cycle is pure schema drift on operations we already manage — no paths
were added or removed from the managed surface. Most of the delta is newly
expanded nested component schemas pulled in by existing operations (e.g.
DashboardPatchTileOpenApi,WidgetDateRange,ErrorTrackingListWidgetConfig,SessionReplayListWidgetConfig,MinimalFeatureFlag,ExperimentMetricOutlierHandling,TeamWorkflowsConfig).New operationIds added to the filter
None. The drift report's "new operationIds" list is the static complement of
our curated allowlist (~71 ops out of ~2095 live ops) — it is not a set of
endpoints that newly appeared this cycle. Everything on it is intentionally
unmanaged: sub-resource actions (
*_activity,*_sharing,*_logs), internal/admin/debug surfaces (
wizard_*,*_kernel_*,sandbox_*,signals_scout_*,tasks_runs_*), and PUT (*_update) duplicates of PATCH verbs we already trackand that no client consumes. An automated schema refresh deliberately does not
expand the managed resource families; that's a human curation decision.
Resources touched
src/resources/dashboard/client.ts): the live spec renamed thedashboards_partial_updaterequest-body componentPatchedDashboard→PatchedPatchedDashboardOpenApi. Updated thePatchedDashboardBodytype alias to match. No behavior change; minimal edit.Unresolved drift
None.
pnpm typecheckpasses.pnpm testpasses (291 tests) — one test,src/pull/run.test.ts > writes files and calls tagOnServer on a non-dry run,flaked on a 500 ms timeout under full-suite parallel load and passes
deterministically in isolation; it does not touch the dashboard schema and is
unrelated to this refresh.
Operations removed from the live spec
None. All managed operationIds in
openapi-filter.yamlare still present inthe live spec.
TaskRun:
e4980cc3-e437-4d44-888f-d164247f4034🤖 Generated with Claude Code