Skip to content

chore(protocol): regenerate OpenAPI document - #60228

Merged
arvsrn merged 1 commit into
devfrom
regenerate-openapi
Oct 29, 2026
Merged

arvsrn merged 1 commit into
devfrom
regenerate-openapi

Conversation

@arvsrn

@arvsrn arvsrn commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

The Effect 4.0.6 upgrade (#59630) changed the generated schema, so check:generated fails on dev and blocks every PR's required unit (linux) check.

This regenerates packages/protocol/openapi.json with bun run generate. The only change is maximum: 9007199254740991 on three integer fields. Regenerating the client produces no changes.

  • bun run script/generate-openapi.ts --check passes.

Added by the opencode bot (AI-generated).

Public API: OpenAPI spec documents maximum: MAX_SAFE_INTEGER on times, remainingRuns, runCount (backwards compatible, generated clients unchanged)

@opencodejr opencodejr Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I ran bun run check:generated in packages/protocol: it fails on the base with "Generated OpenAPI document is stale" and passes on this branch. Regenerating packages/client with its check:generated gives no diff.

Public API: the OpenAPI spec now documents maximum: 9007199254740991 (Number.MAX_SAFE_INTEGER) on the integer fields times, remainingRuns and runCount. This describes an existing bound and the generated clients don't change, so it is backwards compatible.

No concerns.

@arvsrn
arvsrn merged commit 4a05d11 into dev Oct 29, 2026
23 checks passed
@arvsrn
arvsrn deleted the regenerate-openapi branch October 29, 2026 14:00
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