The thread-parent schema changes cannot ship as @undefineds.co/models@0.2.37 because that registry version already exists. Version 0.2.39 is the next open models release version after the published 0.2.38 line.

Constraint: npm package versions are immutable once published

Rejected: Reuse 0.2.37 or 0.2.38 | both versions already exist in the registry

Confidence: high

Scope-risk: narrow

Directive: Publish/tag this models commit before or with any LinX release depending on it

Tested: yarn build

Tested: yarn test:ci