chore(codegen): daily schema refresh (2026-05-29)#21
Open
timgl wants to merge 1 commit into
Open
Conversation
Regenerated src/generated/api.d.ts from the live PostHog OpenAPI spec. No changes to openapi-filter.yaml; all changes are additive schema-only (new optional fields and component types) and pose no breakage for our managed resource families. Generated-By: PostHog Code Task-Id: 8315a759-53d2-4ba6-98d8-0a8cd3c3ce0d
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.
Summary
Daily refresh of
src/generated/api.d.tsfrom the live PostHog OpenAPI spec.src/generated/api.d.tsopenapi-filter.yamlchanges: noneWhat changed in the spec
All deltas are additive component-schema updates — no breaking removals or renames inside the operations our filter exposes. Highlights:
warnings: DataWarehouseSyncWarning[] | nullfield on most query response schemas (Trends, Funnels, Retention, Lifecycle, Stickiness, HogQL, etc.) flagging stale or failed warehouse-source syncs.DataWarehouseSyncWarning,CalendarHeatmapFilter,ExperimentMetricOutlierHandling,ParserMode,Response7.AggregationPropertyType1renamed toAggregationPropertyType(used only inexperiments_create_exposure_cohort_for_experiment_create— outside our filter).resultCustomizationsadded to chart filter schemas; newcohortLabelStartIndexfield; new experiment metric math fields (math,math_property,math_group_type_index,math_hogql,ignore_zeros,lower_bound_percentile,upper_bound_percentile,denominator_outlier_handling,numerator_outlier_handling).kindconstants (cosmetic).New operationIds added to the filter
None. The drift report surfaced ~1,200 operationIds that exist in the live spec but are not in
openapi-filter.yaml. None of them close a CRUD gap for an existing managed resource family — they are sub-resources (sharing, collaborators, activity), bulk helpers, or belong to unmanaged resource families.A few things worth a human's eye for a future PR:
*_update) operations for resources we currently only manage via PATCH (*_partial_update):cohorts_update,event_definitions_update,experiment_holdouts_update,experiment_saved_metrics_update,experiments_update. PATCH is sufficient for our IaC use case so they are intentionally omitted.annotations,surveys,alerts,early_access_feature,notebooks,hog_functions,hog_flows,error_tracking_*, etc. Adding any of these is significant scope (Zod schema + pipeline + diff + execute wiring + tests) and should go through theadd-resourceskill in a dedicated PR, not a daily refresh.Unresolved drift
None. No operationIds previously in
openapi-filter.yamlhave disappeared from the live spec.TaskRun
Task-Id:
8315a759-53d2-4ba6-98d8-0a8cd3c3ce0d