Skip to content

fix(session): use finite archived timestamp schema#25275

Merged
kitlangton merged 1 commit intodevfrom
kit/httpapi-response-schema-parity
May 1, 2026
Merged

fix(session): use finite archived timestamp schema#25275
kitlangton merged 1 commit intodevfrom
kit/httpapi-response-schema-parity

Conversation

@kitlangton
Copy link
Copy Markdown
Contributor

@kitlangton kitlangton commented May 1, 2026

Summary

  • Use Schema.Finite for session archive timestamps so generated OpenAPI/SDK types stay number without non-finite string literal arms.
  • Keep negative archive timestamp values accepted for legacy compatibility while rejecting values that cannot round-trip through JSON.
  • Add bridge coverage for the SDK-affecting session update request schema.

Validation

  • bun typecheck
  • bun run test test/server/httpapi-bridge.test.ts test/server/httpapi-mcp-oauth.test.ts
  • pre-push bun turbo typecheck

@kitlangton kitlangton force-pushed the kit/httpapi-response-schema-parity branch from 1f7bd90 to cb8f181 Compare May 1, 2026 11:48
@kitlangton kitlangton changed the title fix(httpapi): stabilize public OpenAPI schema fix(session): use finite archived timestamp schema May 1, 2026
@kitlangton kitlangton enabled auto-merge (squash) May 1, 2026 11:52
@kitlangton kitlangton merged commit 16ddf5f into dev May 1, 2026
12 checks passed
@kitlangton kitlangton deleted the kit/httpapi-response-schema-parity branch May 1, 2026 11:57
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