v0.34.0

Added

• Added Config.ReindexerIndexNames and ReindexerIndexNamesDefault() so the reindexer's target indexes can be customized from the public API. PR #1194.

Fixed

• Upon a client gaining leadership, its queue maintainer is given more than one opportunity to start. PR #1184.

v0.33.0

Changed

• Jobs erroring or panicking no longer logs at the error/warn level because this is not indicative of a problem inside of River itself. These log statements have been demoted to info. PR #1190.

Fixed

• Fix in Client.Start where previously it was possible for a River client that only partially started before erroring to not try to start on subsequent Start invocations. PR #1187.

v0.32.0

Added

• riverlog.Middleware now supports MiddlewareConfig.MaxTotalBytes (default 8 MB) to cap total persisted river:log history per job. When the cap is exceeded, oldest log entries are dropped first while retaining the newest entry. Values over 64 MB are clamped to 64 MB. PR #1157.

Changed

• Improved riverlog performance and reduced memory amplification when appending to large persisted river:log histories. PR #1157.
• Reduced snooze-path memory amplification by setting snoozes in metadata updates before marshaling, avoiding an extra full-payload JSON rewrite. PR #1159.
• Schema names are now quoted in SQL operations, enabling the use of spaces and other odd characters. PR #1175.

Fixed

• riverpgxv5 now adapts JSON parameters for simple protocol / exec query modes so []byte JSON payloads are not encoded as bytea in pgx text-mode execution paths. This fixes invalid JSON syntax errors when running through protocol-constrained setups like PgBouncer transaction pooling while preserving normal behavior for explicit bytea parameters. Fixes #1153. PR #1155.

v0.31.0

Added

• Added root River CLI flag --statement-timeout so Postgres session statement timeout can be set explicitly for commands like migrations. Explicit flag values take priority over database URL query params, and query params still take priority over built-in defaults. PR #1142.

Changed

• Upgrade supported Go versions to 1.25 and 1.26, and update CI accordingly. PR #1144.

Fixed

• JobCountByQueueAndState now returns consistent results across drivers, including requested queues with zero jobs, and deduplicates repeated queue names in input. This resolves an issue with the sqlite driver in River UI reported in riverqueue/riverui#496. PR #1140.
• Fix connection leak in Listener.Connect in case where afterConnectExec failed. Thanks Johan Kjölhede (@GiGurra)! PR #1147.
• Fix missing ticker.Stop in producer's pollForSettingChanges (@GiGurra). PR #1148.
• Fix accidental use of cancelled context for Notifier.Ping (@GiGurra). PR #1149.
• Add jitter to fetch poll loop to prevent producer stampeding (@GiGurra). PR #1150.

v0.30.2

Fixed

• Fix bug in worker-level stuck job detection. PR #1133.

v0.30.1

Fixed

• Stuck job detection now accounts for worker-level timeouts as well as client-level timeouts. PR #1125.

v0.30.0

Fixed

• Fix possible nil pointer panic when using nil opts in Migrator.MigrateTx. PR #1117.

v0.29.0

Added

• Added HookPeriodicJobsStart that can be used to run custom logic when a periodic job enqueuer starts up on a new leader. PR #1084.
• Added Client.Notify().RequestResign and Client.Notify().RequestResignTx functions allowing any client to request that the current leader resign. PR #1085.
• Basic stuck detection after a job's exceeded its timeout and still not returned after the executor's initiated context cancellation and waited a short margin for the cancellation to take effect. PR #1097.
• Added Client.JobUpdate which can be used to persist job output partway through a running work function instead of having to wait until the job is completed. PR #1098.

Changed

• Add a little more error flavor for when encountering a deadline exceeded error on leadership election suggesting that the user may want to try increasing their database pool size. PR #1101.
• When migrating without an outer transaction, insert/delete version rows immediately after executing migration SQL so that in case a later migration fails, the migrator knows where to restart from. PR #1106.

v0.28.0

Added

• Added riverlog.LoggerSafely which provides a non-panic variant of riverlog.Logger for use when code may or may not have a context logger available. PR #1093.

v0.27.1

• Unique args: Handle embedded fields that are not structs. PR #1088.
• Fix stack overflow when handling river:"unique" annotations on recursive types. PR #1090.