From a5c52255ea5d120c01e76d63a27818fc4052979a Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Fri, 12 Jun 2026 10:40:00 -0700 Subject: [PATCH] =?UTF-8?q?docs(test):=20correct=20the=20v116=20reference?= =?UTF-8?q?=20=E2=80=94=20the=20table=20shipped=20as=20migration=20v117?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- test/e2e/volunteer-context-postgres.test.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/e2e/volunteer-context-postgres.test.ts b/test/e2e/volunteer-context-postgres.test.ts index 9f8505f2f..a516fdd53 100644 --- a/test/e2e/volunteer-context-postgres.test.ts +++ b/test/e2e/volunteer-context-postgres.test.ts @@ -1,11 +1,11 @@ /** * v0.43 (#2095) — volunteer_context on REAL Postgres (engine parity beyond - * PGLite) + the RLS pin for the v116 table. + * PGLite) + the RLS pin for the v117 table. * * The unit suite covers the volunteer core hermetically on PGLite; this file * proves the same op handler against pgvector Postgres: resolution arms, * the fire-and-forget event sink landing rows, the stats join, and that - * context_volunteer_events has ROW LEVEL SECURITY enabled (the v35 + * context_volunteer_events (migration v117) has ROW LEVEL SECURITY enabled (the v35 * auto_rls_on_create_table event trigger covers migration-created tables — * this is the assertion that keeps that mechanism honest for new tables). * @@ -84,7 +84,7 @@ describePg('volunteer_context on real Postgres (#2095)', () => { expect(stats.total_used).toBeGreaterThanOrEqual(1); }, 120_000); - test('RLS is enabled on context_volunteer_events (auto-RLS covers v116)', async () => { + test('RLS is enabled on context_volunteer_events (auto-RLS covers v117)', async () => { const engine = getEngine(); const rows = await engine.executeRaw<{ relrowsecurity: boolean }>( `SELECT relrowsecurity FROM pg_class