| Files | Last commit | Last update |
|---|---|---|
Test the upgrade from every released pre-registry schema (#2435) * Test the upgrade from the released v3, v4 and v6 schemas The old tests made a v3 database from the current schema. These fixtures use the DDL that v0.1.12, v0.1.15 and v0.2.1 shipped, with data in each table and the marker sets that a new install and an upgrade wrote. They check that each upgrade to version 43 keeps the rows, matches a new install, passes the foreign-key and integrity checks, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the foreign-key and history guards of the migration runner No test made the foreign-key check before commit reject a migration. The new test puts a broken foreign key in a v27 and a v42 database. Migration 28 (which turns foreign keys off) and migration 43 must roll back, keep every row, and turn foreign keys on again. A table-driven test also rejects a history with a gap at each version from 8 to 42. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test migration 21 with case variants and a failed run The old test seeded only `computer_use` and `computer_use_saved`. The version 20 name index is case-sensitive, so `Computer_Use` and `COMPUTER_USE_SAVED` could also exist. The new test checks that the migration renames each case variant to a different free name, keeps the configuration, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the workspace root rewrite of migration 13 No test checked the `OpenBot/Bots` to `OpenBot/Agents` rewrite. The new test stores POSIX, Windows and JSON-escaped paths in JSON and raw columns. It checks that each stored root moves once, that `Botsy` and a user's own `Projects/OpenBot/Bots` stay, and that a failed run rolls back and retries. It also records that an agent which keeps its id gets the new root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the upgrade from the released v0.1.18 schema v0.1.18 to v0.2.0 kept schema version 4 but added the thread_messages_page_order index. Add its DDL as a released schema and upgrade it with markers [4] and [3, 4]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 27 days ago | |
Test the upgrade from every released pre-registry schema (#2435) * Test the upgrade from the released v3, v4 and v6 schemas The old tests made a v3 database from the current schema. These fixtures use the DDL that v0.1.12, v0.1.15 and v0.2.1 shipped, with data in each table and the marker sets that a new install and an upgrade wrote. They check that each upgrade to version 43 keeps the rows, matches a new install, passes the foreign-key and integrity checks, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the foreign-key and history guards of the migration runner No test made the foreign-key check before commit reject a migration. The new test puts a broken foreign key in a v27 and a v42 database. Migration 28 (which turns foreign keys off) and migration 43 must roll back, keep every row, and turn foreign keys on again. A table-driven test also rejects a history with a gap at each version from 8 to 42. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test migration 21 with case variants and a failed run The old test seeded only `computer_use` and `computer_use_saved`. The version 20 name index is case-sensitive, so `Computer_Use` and `COMPUTER_USE_SAVED` could also exist. The new test checks that the migration renames each case variant to a different free name, keeps the configuration, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the workspace root rewrite of migration 13 No test checked the `OpenBot/Bots` to `OpenBot/Agents` rewrite. The new test stores POSIX, Windows and JSON-escaped paths in JSON and raw columns. It checks that each stored root moves once, that `Botsy` and a user's own `Projects/OpenBot/Bots` stay, and that a failed run rolls back and retries. It also records that an agent which keeps its id gets the new root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the upgrade from the released v0.1.18 schema v0.1.18 to v0.2.0 kept schema version 4 but added the thread_messages_page_order index. Add its DDL as a released schema and upgrade it with markers [4] and [3, 4]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 27 days ago | |
Test the upgrade from every released pre-registry schema (#2435) * Test the upgrade from the released v3, v4 and v6 schemas The old tests made a v3 database from the current schema. These fixtures use the DDL that v0.1.12, v0.1.15 and v0.2.1 shipped, with data in each table and the marker sets that a new install and an upgrade wrote. They check that each upgrade to version 43 keeps the rows, matches a new install, passes the foreign-key and integrity checks, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the foreign-key and history guards of the migration runner No test made the foreign-key check before commit reject a migration. The new test puts a broken foreign key in a v27 and a v42 database. Migration 28 (which turns foreign keys off) and migration 43 must roll back, keep every row, and turn foreign keys on again. A table-driven test also rejects a history with a gap at each version from 8 to 42. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test migration 21 with case variants and a failed run The old test seeded only `computer_use` and `computer_use_saved`. The version 20 name index is case-sensitive, so `Computer_Use` and `COMPUTER_USE_SAVED` could also exist. The new test checks that the migration renames each case variant to a different free name, keeps the configuration, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the workspace root rewrite of migration 13 No test checked the `OpenBot/Bots` to `OpenBot/Agents` rewrite. The new test stores POSIX, Windows and JSON-escaped paths in JSON and raw columns. It checks that each stored root moves once, that `Botsy` and a user's own `Projects/OpenBot/Bots` stay, and that a failed run rolls back and retries. It also records that an agent which keeps its id gets the new root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the upgrade from the released v0.1.18 schema v0.1.18 to v0.2.0 kept schema version 4 but added the thread_messages_page_order index. Add its DDL as a released schema and upgrade it with markers [4] and [3, 4]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 27 days ago | |
Test the upgrade from every released pre-registry schema (#2435) * Test the upgrade from the released v3, v4 and v6 schemas The old tests made a v3 database from the current schema. These fixtures use the DDL that v0.1.12, v0.1.15 and v0.2.1 shipped, with data in each table and the marker sets that a new install and an upgrade wrote. They check that each upgrade to version 43 keeps the rows, matches a new install, passes the foreign-key and integrity checks, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the foreign-key and history guards of the migration runner No test made the foreign-key check before commit reject a migration. The new test puts a broken foreign key in a v27 and a v42 database. Migration 28 (which turns foreign keys off) and migration 43 must roll back, keep every row, and turn foreign keys on again. A table-driven test also rejects a history with a gap at each version from 8 to 42. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test migration 21 with case variants and a failed run The old test seeded only `computer_use` and `computer_use_saved`. The version 20 name index is case-sensitive, so `Computer_Use` and `COMPUTER_USE_SAVED` could also exist. The new test checks that the migration renames each case variant to a different free name, keeps the configuration, and rolls back and retries after a failure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the workspace root rewrite of migration 13 No test checked the `OpenBot/Bots` to `OpenBot/Agents` rewrite. The new test stores POSIX, Windows and JSON-escaped paths in JSON and raw columns. It checks that each stored root moves once, that `Botsy` and a user's own `Projects/OpenBot/Bots` stay, and that a failed run rolls back and retries. It also records that an agent which keeps its id gets the new root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Test the upgrade from the released v0.1.18 schema v0.1.18 to v0.2.0 kept schema version 4 but added the thread_messages_page_order index. Add its DDL as a released schema and upgrade it with markers [4] and [3, 4]. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 27 days ago |
| Files | Last commit | Last update |
|---|---|---|
| 27 days ago | ||
| 27 days ago | ||
| 27 days ago | ||
| 27 days ago |