Shipped · Databases

What typeorm/typeorm shipped

The public repository of Typeorm · github.com/typeorm/typeorm

Written by FoxPlug from the repository's own releases; not affiliated with Typeorm. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/typeorm/typeorm; Typeorm did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

Follow typeorm's weekly shipped digest

Week of October 5, 2026

What shipped

Why it matters

This week brought a 1.1.2 release and a set of fixes for everyday problems: connection leaks in DataSource.initialize(), hangs on CockroachDB shutdown, dropped date edits under the utc flag, and invalid SQL Server lock hints. Users on SQL Server, Postgres, CockroachDB and closure-table entities should see fewer stuck queries and stale data after saving.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

1.1.2 is out. Fixes this week: DataSource.initialize() connection leaks, CockroachDB destroy hangs, utc date column edits dropped west of UTC, SQL Server lock hints in nested joins, and locks held after subscriber errors.

Post for LinkedIn

TypeORM 1.1.2 is now released. Alongside the release, this week's changes fix several issues that affected everyday use. DataSource.initialize() no longer leaks connections under concurrent calls or failed driver connects, and DataSource.destroy() no longer hangs on CockroachDB with multiple connected query runners. Date columns declared with utc: true now detect changes correctly when the process runs west of UTC, SQL Server setLock() queries with two-level relation chains generate valid T-SQL, and SQL Server query locks are released when subscriber hooks throw. Closure-table reparenting reads primary values through column metadata so cross-root moves stay consistent, and spatial columns without an explicit feature type or SRID are compared against the reported defaults.

Week of September 28, 2026

What shipped

Why it matters

This week focused on bug fixes for data integrity and deployment reliability. The composite primary key fix addresses a critical issue that could cause data loss in hydration, while schema metadata and CI fixes ensure the project builds and deploys correctly across its workspace setup.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

TypeORM updates: fixed composite primary key hydration collisions that caused data loss, corrected schema metadata handling, and resolved documentation deployment issues.

Post for LinkedIn

TypeORM shipped critical fixes this week: composite primary keys no longer collide during hydration (preventing data loss), user-defined schemas are correctly stored in metadata, and documentation builds are now stable with the new pnpm workspace layout. These improvements enhance data reliability and project maintainability.

More from typeorm/typeorm on GitHub

Merged pull requests

Weeks with too little public activity are left out rather than filled in. Last updated 2026-10-12.

Is this your repo? Ask us to remove this page.