build(deps): Bump pg-boss from 12.25.1 to 12.26.0 in the npm-production group

[dependabot]

Bumps the npm-production group with 1 update: pg-boss.

Updates pg-boss from 12.25.1 to 12.26.0

Release notes

Sourced from pg-boss's releases.

12.26.0

Schema version: 37 (migrates automatically on start() / migrate).

This release adds schema drift detection, self-healing for background index builds, and a set of correctness fixes. A few of those fixes surface errors that earlier versions silently swallowed — see Behavior changes before upgrading.

Highlights

Schema drift detection

• New boss.detectSchemaDrift() — compares the live database against the shape pg-boss expects (tables, indexes, functions, columns, enum, constraints) and returns a structured SchemaDriftReport. It only reports; it never modifies the schema.
• New CLI command: pg-boss doctor — runs the same scan and prints missing / invalid / mismatched objects with copy-paste remediation DDL. Exit code 1 on drift, 0 when clean.
• Drift comparison is backend-aware: type/default/constraint checks are Postgres-canonical and are skipped on CockroachDB (which renders catalog text differently), while presence checks run everywhere. Catalog queries a backend doesn't support (e.g. pg_get_functiondef) are skipped rather than reported as false drift.
• A canonical schema manifest (src/schema.json) is generated from a real install and validated in CI (npm run gen:manifest:check, wired into pretest), so the expected shape can never silently drift from the DDL.

Background index build (BAM) health & healing

• Interrupted CREATE INDEX CONCURRENTLY builds are detected and healed: a re-attempted build that finds an invalid leftover index drops and rebuilds it, instead of the command's IF NOT EXISTS skipping over a broken index forever. A valid index is never dropped.
• Stalled builds are reclaimed using a cluster-wide pg_locks liveness check (the ShareUpdateExclusiveLock a CREATE INDEX CONCURRENTLY holds on its table for the whole build): a genuinely running build is never reclaimed (no matter how long it runs), a dead one recovers within minutes, and the check stays correct when many pg-boss instances share one database. Backends that roll interrupted builds back (CockroachDB, YugabyteDB) fall back to a timeout-only reclaim.

Behavior changes

These are bug fixes for cases where pg-boss previously resolved successfully while hiding a failure. Under strict semver they are behavior changes; they ship in this minor release. Ensure an error listener is attached to the boss instance, and handle rejections from direct fetch() / deleteQueue() / insert() calls.

• fetch() / work() now surface database errors. Previously every fetch error was swallowed and returned as an empty batch — a DB outage was indistinguishable from an empty queue. Now only a unique-constraint violation (SQLSTATE 23505, the benign concurrent-slot race) is treated as an empty fetch; any other error propagates. In a work() loop it is routed to the worker's error handler and emitted as an error event; a direct fetch() call now rejects.
• insert() rejects on duplicate job ids within a batch. Passing the same explicit id twice in one insert([...]) now throws duplicate job id in insert batch: <id> instead of silently deduplicating via ON CONFLICT DO NOTHING.
• deleteQueue() now propagates DELETE / cache-eviction errors. A transient failure during the delete previously resolved as success while the queue survived; it now rejects. Deleting a queue that does not exist remains a no-op.

Other fixes

• knex adapter: queries mixing jsonb ? key-exists operators with $N placeholders (e.g. updateJob) no longer throw Undefined binding(s) detected — literal ? operators are escaped before binding.
• retryBackoff: true with no retryDelay now backs off (#839). The default retryDelay of 0 made the exponential-backoff formula (retryDelay * 2^n) evaluate to 0, so retries fired instantly with no backoff. The delay is now floored to 1 second in the backoff path when retryDelay is unset, matching the documented default. The fixed-delay path (retryBackoff off) still honors an explicit retryDelay: 0 as immediate retry.
• update() honors startAfter: 0 (and negative values) to pull a deferred job forward to now, instead of silently dropping the edit.
• LISTEN/NOTIFY reconnect: the listener only self-heals after it has connected at least once, so a failed initial connect falls back to polling cleanly without leaking an untracked reconnect.
• Migration floor guard: migrating from a DB version below the oldest supported starting version now fails with a clear message instead of applying migrations over missing steps.
• job_table_format migration (v37): the table-name rewrite is anchored so it matches only the base table reference and bare job_iN tokens.
• Internal hardening: start/stop refactor with ret/re-entrancy safety, clock-skew handling in the timekeeper, a group-counter leak fix, and dead-letter insert parameter alignment.

Upgrade notes

• No manual migration required — start() (or pg-boss migrate) moves the schema to v37.
• After upgrading, attach an error listener if you don't already have one; the fetch change means genuine DB errors now reach it.
• Optionally run pg-boss doctor to verify the live schema matches the expected shape.

Dependencies

• Dev-dependency bumps: @electric-sql/pglite, @types/node, kysely, tsx.

Full Changelog: timgit/pg-boss@12.25.1...12.26.0

Commits

• 31a4cf0 Merge pull request #843 from timgit/bugfix-2607
• 72e48c3 fix pglite test
• 2276d34 fix retry backoff when retry delay is missing
• ab6ffc2 cli docs
• 45b593a switch to pg_locks for bam race conditions
• cf1eb0a fixes and types
• 57054e2 updates to schema manifest
• 1f5ec22 drop git dep for ci
• b336920 added schema manifest and build script
• e4035a4 more drift detection
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Labels

The following labels could not be found: dependencies, javascript. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
autonomous-ehs-management	Ready	Preview, Comment	Jul 12, 2026 10:29am

[github-actions]

🎉 This PR is included in version 1.4.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀