Claude Bot 5d661a4487 fix(sql): return JS number for PostgreSQL bigint values within safe integer range ...

When the `bigint` option is not set (the default), PostgreSQL int8/bigint
values that fit within Number.MAX_SAFE_INTEGER (±2^53-1) are now returned
as JavaScript numbers instead of strings. Values outside that range continue
to be returned as strings to avoid precision loss. This makes common
operations like COUNT(*) return numbers as users expect.

Fixes #22188

Co-Authored-By: Claude <noreply@anthropic.com>

2026-02-14 23:48:15 +00:00

..

bun

update(crypto): update root certificates to NSS 3.119; eliminate external HTTPS in tests (#27020)

2026-02-14 02:47:13 -08:00

deno

Deflake a test

2024-12-12 02:07:29 -08:00

first_party

feat(websocket): add HTTP/HTTPS proxy support (#25614)

2026-01-08 16:21:34 -08:00

junit-reporter

feat(test): add --retry flag and emit separate testcase entries for retries in JUnit XML (#26866)

2026-02-10 10:58:21 -08:00

node

update(crypto): update root certificates to NSS 3.119; eliminate external HTTPS in tests (#27020)

2026-02-14 02:47:13 -08:00

sql

fix(sql): return JS number for PostgreSQL bigint values within safe integer range

2026-02-14 23:48:15 +00:00

third_party

@types/bun: Update to @types/node@25, fallback to PropertyKey in test expect matchers when keyof unknown is used (#25460)

2025-12-10 18:15:55 -08:00

valkey

fix(test): update valkey test snapshots for Redis 8 error message format (#26878)

2026-02-10 16:30:55 -08:00

web

update(crypto): update root certificates to NSS 3.119; eliminate external HTTPS in tests (#27020)

2026-02-14 02:47:13 -08:00

workerd

fix(test): eliminate external HTTPS fetches and renew expired TLS certs (#27013)

2026-02-13 20:45:06 -08:00