• Remove deprecated width and zerofill column options from all interfaces and implementations
• Delete width/zerofill handling from MySQL, Aurora-MySQL, and CockroachDB drivers
• Remove width entries from dataTypeDefaults for MySQL integer types
• Delete tests and test entities specific to width/zerofill functionality
• Add migration guide documenting the removal and recommended alternatives

Remove zerofill option from numeric column options

src/decorator/options/ColumnNumericOptions.ts

Remove width and zerofill from column options interface

src/decorator/options/ColumnOptions.ts

Remove width and zerofill from unsigned options interface

src/decorator/options/ColumnUnsignedOptions.ts

Description

zerofill previously implied unsigned, but after this change unsigned is only set when
explicitly provided. The migration guide tells users to remove zerofill without noting they may
need to add unsigned: true, which can cause schema sync/migration generation to attempt dropping
UNSIGNED on existing columns and on relation/junction columns derived from them.

Code

docs/docs/guides/8-migration-v1.md[R19-34]

+### `width` and `zerofill` column options removed
+
+MySQL 8.0.17 deprecated display width for integer types and the `ZEROFILL` attribute, and MySQL 8.4 removed them entirely. TypeORM no longer supports the `width` and `zerofill` column options. If you were using these options, remove them from your column definitions:
+
+```typescript
+// Before
+@Column({ type: "int", width: 9, zerofill: true })
+postCode: number
+
+// After
+@Column({ type: "int" })
+postCode: number
+```
+
+If you need zero-padded display formatting, handle it in your application layer using `String.prototype.padStart()` or the MySQL `LPAD()` function in a raw query. The `unsigned` option for integer types is **not** affected by this change and continues to work as before.
+

Evidence

The guide’s example removes zerofill and does not add unsigned. In code,
ColumnMetadata.unsigned is now only set when unsigned is explicitly present, so removing
zerofill can change metadata from unsigned->signed. Schema diff logic still treats unsigned
mismatches as a column change, which can produce ALTERs. Relation/junction columns inherit
unsigned from the referenced column metadata, so they can be impacted too.

docs/docs/guides/8-migration-v1.md[19-34]
src/metadata/ColumnMetadata.ts[404-406]
src/query-runner/BaseQueryRunner.ts[583-595]
src/driver/mysql/MysqlDriver.ts[1032-1041]
src/metadata-builder/JunctionEntityMetadataBuilder.ts[115-121]
src/schema-builder/table/TableColumn.ts[146-156]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The migration guide instructs users to remove `zerofill`, but it does not mention that `zerofill` previously implied `unsigned` in TypeORM/MySQL semantics. After this PR, `unsigned` is only set when explicitly provided, so following the guide literally can create a metadata-vs-database mismatch and lead to unexpected schema diffs / generated ALTER statements.

### Issue Context
- `ColumnMetadata` no longer forces `unsigned = true` when `zerofill` was set.
- Schema diff logic still treats `unsigned` mismatches as a column change.
- Relation/junction columns propagate `unsigned` from referenced columns.

### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[19-34]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools