[waleedlatif1]

Summary

• CSV import inferred a column as number whenever every sampled value parsed with Number(), so ZIP codes, phone numbers, and SKUs like 02134 were stored as 2134 and the leading zero was lost for good
• inferColumnType now treats a value with a leading zero followed by another digit as text; 0, 0.5, and -0.5 still infer as numbers
• Covers new-table imports and new columns added during an append import (both use the same inference)

Type of Change

• Bug fix

Testing

• Regression test in lib/table/import.test.ts, shown red on the pre-fix code, green after
• lib/table/import.test.ts + lib/table/import-runner.test.ts pass (47 tests)
• biome on changed files; full type-check/audits left to CI

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Nov 6, 2026 8:36pm UTC

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This PR appears safe to merge.

Summary

Keeps leading-zero CSV codes as text when choosing types for new tables and newly added columns.

• CSV imports keep codes with leading zeros in text columns.

_{Reviews (1) · Last reviewed commit: "fix(tables): keep leading-zero codes as ..." · Reviewed by Greptile}