chore(codegen): daily schema refresh (2026-06-19)#41
Open
timgl wants to merge 1 commit into
Open
Conversation
Regenerate src/generated/api.d.ts from the live PostHog OpenAPI schema. Changes are additive evolution of already-managed resource component schemas (new query kinds, dashboard widget configs, experiment metadata, sync warnings) plus one breaking rename: the dashboard PATCH request body schema `PatchedDashboard` became `PatchedPatchedDashboardOpenApi`. Updated the dashboard client's type reference to match; the field shape (name, tags, restriction_level, tiles) is unchanged. No new operationIds added to openapi-filter.yaml. No managed operationIds disappeared from the live spec. Generated-By: PostHog Code Task-Id: 260bfeb3-e2be-4a6a-8e44-c5a703930237
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
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-19
Regenerated
src/generated/api.d.tsfrom the live PostHog OpenAPI schema(
https://us.posthog.com/api/schema/?format=json, filtered byopenapi-filter.yaml).No hand-edits to the generated file — produced via
pnpm codegen.Spec diff size
src/generated/api.d.ts: +1830 / −138 (1 file)AccountsQuery,AccountsQueryResponse,CalendarHeatmapFilter,DashboardPatchTileOpenApi,DashboardPatchWidgetOpenApi,DataWarehouseSyncWarning,ActivityEventsListWidgetConfig/ErrorTrackingListWidgetConfig/ExperimentsListWidgetConfig/ExperimentResultsWidgetConfig/SessionReplayListWidgetConfig,ExperimentExposureEstimateConfig,ExperimentMetricOutlierHandling,ExperimentRunningTimeCalculation,FeatureFlagExperimentSetMetadata,MinimalFeatureFlag,TeamCustomerAnalyticsConfig,TeamWorkflowsConfig, and dashboard widgetfilter helpers. New enum values include
ChartDisplayType: "SlopeGraph"andfour
AvailableSetupTaskIdsEnumentries (use_posthog_ai,use_posthog_code,use_posthog_mcp,use_posthog_in_slack).PatchedDashboard→PatchedPatchedDashboardOpenApi. Field shape (name,tags,restriction_level,tiles) is unchanged.New operationIds added to the filter
None. The drift detector reports every live-spec operationId absent from
openapi-filter.yaml— i.e. the entire unfiltered PostHog API surface (~hundredsof ops across error-tracking, warehouse, llm-analytics, surveys, etc.). The filter
is a deliberately curated allowlist of CRUD on the managed IaC resources
(insights, dashboards, feature flags, endpoints, event definitions, schema
property groups, event schemas, experiment holdouts/saved-metrics, experiments,
environments, cohorts, actions). None of the reported ops extend a managed family
with anything the IaC client needs (the rest are auxiliary endpoints —
sharing/activity/bulk-tag/PUT-variants — or brand-new product surfaces). Adopting
a new resource family is a deliberate human decision via the
add-resourceskill,not an automated daily-refresh action, so nothing was added.
Resources touched
src/resources/dashboard/client.ts— updated one type alias fromcomponents["schemas"]["PatchedDashboard"]tocomponents["schemas"]["PatchedPatchedDashboardOpenApi"]to track the rename.Minimal, no behavior change.
Unresolved drift / removals
entries are still present in the regenerated schema. Nothing to flag for human
deletion this run.
Verification
pnpm typecheck✅pnpm test✅ (291/291; onepull/run.test.ts500ms timeout is load-flaky andpasses in isolation / on re-run — unrelated to the schema)
Generated by the daily schema-refresh agent · TaskRun
260bfeb3-e2be-4a6a-8e44-c5a703930237