Skip to content

chore: regenerate Java SDK from oas-ci pipeline#156

Draft
jabrowne-te wants to merge 1 commit intomainfrom
oas-ci
Draft

chore: regenerate Java SDK from oas-ci pipeline#156
jabrowne-te wants to merge 1 commit intomainfrom
oas-ci

Conversation

@jabrowne-te
Copy link
Copy Markdown
Contributor

Summary

  • Regenerated Java SDK modules using the new OpenAPI build toolchain (openapi-format) via the oas-ci pipeline
  • No semantic API changes - all differences are cosmetic (whitespace, float/integer literals, property ordering) or intentional removals (features hidden by prod overlays)
  • The core module is not generated and remains unchanged

Changes

  • 331 files changed (+909 / -1296)
  • Cosmetic differences: minor whitespace in Javadoc, 100.0100 in example literals, property reordering in generated models
  • Intentional removals (6 files deleted - models hidden by prod overlays):
    • dashboards: ApiAgentWidgetShow, ApiAgentWidgetType, ApiWidgetSortDirection, ApiWidgetSortProperty, WidgetType
    • streaming: TagMatchObjectType

Test plan

  • Verify SDK compiles (./gradlew build)
  • Run existing tests
  • Compare API surface against current release

Made with Cursor

Regenerated using the new OpenAPI build toolchain (openapi-format).
No semantic API changes - differences are cosmetic (whitespace,
number formatting, property ordering) and intentional removals
(features hidden by prod overlays).

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant