Skip to content

chore(spec): synchronize Lago OpenAPI - #39

Merged
groyoh merged 3 commits into
mainfrom
automation/openapi-drift
Nov 5, 2026
Merged

groyoh merged 3 commits into
mainfrom
automation/openapi-drift

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Context

The CLI commands are generated from a copy of the Lago OpenAPI document kept in spec/openapi.yaml. A daily job compares this copy with the published document (https://swagger.getlago.com/openapi.yaml) and opens this PR when they differ.

Description

spec/openapi.yaml was replaced with the published document. The generated code, the command reference, the man pages and the shell completions were generated again from it.

Fetched at 2026-11-05T16:03:47Z
Spec version 1.57.0
Spec SHA-256 0548d030b8384508d3638203c453f704565a7df954f4db9e42deadd554b5069e
lago-openapi commit getlago/lago-openapi@134712095952

groyoh
groyoh previously approved these changes Nov 5, 2026
Three tests compared the embedded spec version with the literal `1.52.1`, so
a drift that changes the version failed them. They now read
`generated.SpecVersion`; `TestGeneratedManifestEmbedsPinnedSpecIdentity` still
checks the generated code against `spec/operations.json`.

The body types test skipped body fields that share a name with a path
parameter. Path parameters are positional arguments, so a required body field
such as `--code` on `POST /plans/{code}/charges` keeps its own flag and must be
passed. Only query and header parameters are skipped now.
`TestPinnedOperationsLoaded` only checked that the generated package has a
version, a SHA-256 and operations. `TestGeneratedManifestEmbedsPinnedSpecIdentity`
already checks them against `spec/operations.json`, and the parity test keeps
the operation-count guard.
@groyoh
groyoh merged commit 1f08df6 into main Nov 5, 2026
12 checks passed
@groyoh
groyoh deleted the automation/openapi-drift branch November 5, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant