From c4860968458d8f1c224e85fd4b6ffea4dc5c67d3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Sun, 16 Aug 2026 19:28:11 +0200 Subject: [PATCH] Re-verify the failed-row retention assumptions against pg-boss 12.27.0 The guard pins the installed version alongside the three source facts the 72-hour reader depends on, so a dependency bump has to stop and be looked at rather than sliding past. It did its job here: 12.27.0 tripped the version line. Checked the release against 12.26.0. The retention plan is untouched, all three assertions still match the shipped dist/plans.js verbatim. What moved sits in the fetch path (group concurrency reworked to a keyed JSONB lookup, schema names now routed through normalizeSchemaName / resolveSchemaName) and in start_after, which becomes inclusive so a job written with the default start time is fetchable on the next statement. None of that touches the failed-row ledger. So the assumption holds and the pin moves with it. --- src/lib/jobs/__tests__/job-failures-retention.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/jobs/__tests__/job-failures-retention.test.ts b/src/lib/jobs/__tests__/job-failures-retention.test.ts index e1437bbb2..f098283e1 100644 --- a/src/lib/jobs/__tests__/job-failures-retention.test.ts +++ b/src/lib/jobs/__tests__/job-failures-retention.test.ts @@ -16,7 +16,7 @@ describe("pg-boss failed-row ledger retention", () => { ) as { version: string }; const plans = readFileSync(join(PG_BOSS_ROOT, "dist/plans.js"), "utf8"); - expect(packageJson.version).toBe("12.26.0"); + expect(packageJson.version).toBe("12.27.0"); expect(plans).toContain("retention_seconds: FORTEEN_DAYS"); expect(plans).toContain("deletion_seconds: SEVEN_DAYS"); expect(plans).toContain(