Skip to content

fix(openapi): document Unix-second timestamps as integers - #469

Merged
stakach merged 2 commits into
masterfrom
fix/openapi-epoch-timestamps
Nov 18, 2026
Merged

stakach merged 2 commits into
masterfrom
fix/openapi-epoch-timestamps

Conversation

@stakach

@stakach stakach commented Nov 18, 2026

Copy link
Copy Markdown
Member

Closes #466.

Require json-schema 2.1.2, ActiveModel 4.7.2, and PlaceOS models 9.123.6 so the OpenAPI generator sees the existing epoch converters' schema hints, including on generated response structs. Regenerate the OpenAPI 3.1 document and bump the REST API shard version to 2.0.1.

The generated diff corrects 84 timestamp fields across 40 schemas to integer/Int64 and preserves their existing null alternatives. A comparison of the parsed documents found no other schema or operation changes. The new regression spec also checks RFC 3339 timestamps alongside epoch fields.

Upstream fixes: spider-gazelle/json-schema#6, spider-gazelle/active-model#40, and PlaceOS/models#342.

@github-actions github-actions Bot added the type: bug something isn't working label Nov 18, 2026
@stakach
stakach merged commit 1380cc8 into master Nov 18, 2026
11 checks passed
@stakach
stakach deleted the fix/openapi-epoch-timestamps branch November 18, 2026 06:35
MrYuion added a commit to PlaceOS/ts-client that referenced this pull request Nov 18, 2026
PlaceOS/rest-api#469 documents the Unix-second timestamps as integers, so
the rest-api needs no epoch patch. The staff-api document is not
regenerated yet, so it keeps its list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OpenAPI doc lists Unix-second timestamps as date-time strings

1 participant