Description
@pg-boss/dashboard bundles its own copy of pg-boss, currently 12.28.x (schema 38). When the target database has been migrated to schema v39 by an application running pg-boss 12.29.0, every dashboard route that goes through the internal PgBoss instance fails with:
pg-boss database requires migrations
Affected: job detail pages ("Failed to load job"), and all actions (send, retry, cancel, schedule, unschedule). The list/browse pages still work since they use the dashboard's own SQL pool.
Root cause
async check() {
if (!await this.isInstalled()) throw new Error("pg-boss is not installed");
if (schemaVersion !== await this.schemaVersion()) throw new Error("pg-boss database requires migrations");
}
The strict !== rejects a database schema that is newer than the bundled pg-boss.
Stack trace
Error: pg-boss database requires migrations
at async #doStart (…/@pg-boss/dashboard/build/server/index.js:8897:8)
at async PgBoss.start (…/@pg-boss/dashboard/build/server/index.js:8888:11)
at async getJobById (…/@pg-boss/dashboard/build/server/index.js:9180:23)
at async loader$6 (…/@pg-boss/dashboard/build/server/index.js:13378:14)
at async callRouteHandler (…/react-router/dist/production/lib/server-runtime/data.js:14:15)
Environment
@pg-boss/dashboard 1.6.6 (also reproduced with 1.1.3)
- Database migrated by pg-boss 12.29.0 (schema v39)
- Node.js 24.x, PostgreSQL 15
Thank you
Description
@pg-boss/dashboardbundles its own copy of pg-boss, currently 12.28.x (schema 38). When the target database has been migrated to schema v39 by an application running pg-boss 12.29.0, every dashboard route that goes through the internalPgBossinstance fails with:Affected: job detail pages ("Failed to load job"), and all actions (send, retry, cancel, schedule, unschedule). The list/browse pages still work since they use the dashboard's own SQL pool.
Root cause
The strict
!==rejects a database schema that is newer than the bundled pg-boss.Stack trace
Environment
@pg-boss/dashboard1.6.6 (also reproduced with 1.1.3)Thank you