Skip to content

fix: nullable arrays + node 24 + dev workflow docs#30

Merged
pablaber merged 5 commits intomainfrom
feature/agents-md
May 4, 2026
Merged

fix: nullable arrays + node 24 + dev workflow docs#30
pablaber merged 5 commits intomainfrom
feature/agents-md

Conversation

@pablaber
Copy link
Copy Markdown
Owner

@pablaber pablaber commented May 4, 2026

Summary

  • Fix: nullable arrays in OpenAPI schemas now emit name: Nullable<T[]> instead of the malformed Nullable< name: T[]> (lib/builder/type-builder.ts).
  • Chore: bump to Node 24 (.nvmrc, @types/node ^24.0.0).
  • Chore: modernize CI — add checks.yaml (lint + build), upgrade pr-validate.yaml to amannn/action-semantic-pull-request@v6, upgrade release.yaml to googleapis/release-please-action@v4 with config externalized into release-please-config.json + .release-please-manifest.json.
  • Docs: add AGENTS.md (project guidance + PR conventions) and a ## Development section in README.md covering scripts, manual testing, CI, and the release-please flow.

Validation

  • npm run lint — clean.
  • npm run build — clean under Node 24.15.0.
  • Built ott and ran it against a minimal nullable-array repro YAML; confirmed output (types: Nullable<string[]>, nested_objects?: Nullable<{...}[]>) compiles under tsc --noEmit --strict. Non-nullable arrays and arrays of objects unchanged.

@pablaber pablaber merged commit d842912 into main May 4, 2026
2 checks passed
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