Riverqueue

Although it comes with a number of improvements, there's nothing particularly notable about version 0.1.0. Until now we've only been incrementing the patch version given the project's nascent nature, but from here on we'll try to adhere more closely to semantic versioning, using the patch version for bug fixes, and incrementing the minor version when new functionality is added.

Added

- The River CLI now supports `river bench` to benchmark River's job throughput against a database. [PR 254](https://github.com/riverqueue/river/pull/254).
- The River CLI now has a `river migrate-get` command to dump SQL for River migrations for use in alternative migration frameworks. Use it like `river migrate-get --up --version 3 > version3.up.sql`. [PR 273](https://github.com/riverqueue/river/pull/273).
- The River CLI's `migrate-down` and `migrate-up` options get two new options for `--dry-run` and `--show-sql`. They can be combined to easily run a preflight check on a River upgrade to see which migration commands would be run on a database, but without actually running them. [PR 273](https://github.com/riverqueue/river/pull/273).
- The River client gets a new `Client.SubscribeConfig` function that lets a subscriber specify the maximum size of their subscription channel. [PR 258](https://github.com/riverqueue/river/pull/258).

Changed

- River uses a new job completer that batches up completion work so that large numbers of them can be performed more efficiently. In a purely synthetic (i.e. mostly unrealistic) benchmark, River's job throughput increases ~4.5x. [PR 258](https://github.com/riverqueue/river/pull/258).
- Changed default client IDs to be a combination of hostname and the time which the client started. This can still be changed by specifying `Config.ID`. [PR 255](https://github.com/riverqueue/river/pull/255).
- Notifier refactored for better robustness and testability. [PR 253](https://github.com/riverqueue/river/pull/253).

Fixed

- Fixed a problem in `riverpgxv5`'s `Listener` where it wouldn't unset an internal connection if `Close` returned an error, making the listener not reusable. Thanks mfrister for pointing this one out! [PR 246](https://github.com/riverqueue/river/pull/246).

Fixed

- Fixed a memory leak caused by not always cancelling the context used to enable jobs to be cancelled remotely. [PR 243](https://github.com/riverqueue/river/pull/243).

Added

- `JobListParams.Kinds()` has been added so that jobs can now be listed by kind. [PR 212](https://github.com/riverqueue/river/pull/212).

Changed

- The underlying driver system's been entirely revamped so that River's non-test code is now decoupled from `pgx/v5`. This will allow additional drivers to be implemented, although there are no additional ones for now. [PR 212](https://github.com/riverqueue/river/pull/212).

Fixed

- Fixed a memory leak caused by allocating a new random source on every job execution. Thank you shawnstephens for reporting ❤️ [PR 240](https://github.com/riverqueue/river/pull/240).
- Fix a problem where `JobListParams.Queues()` didn't filter correctly based on its arguments. [PR 212](https://github.com/riverqueue/river/pull/212).
- Fix a problem in `DebouncedChan` where it would fire on its "out" channel too often when it was being signaled continuousy on its "in" channel. This would have caused work to be fetched more often than intended in busy systems. [PR 222](https://github.com/riverqueue/river/pull/222).

Fixed

- Brings in another leadership election fix similar to 217 in which a TTL equal to the elector's run interval plus a configured TTL padding is also used for the initial attempt to gain leadership (217 brought it in for reelection only). [PR 219](https://github.com/riverqueue/river/pull/219).

Changed

- Tweaked behavior of `JobRetry` so that it does actually update the `ScheduledAt` time of the job in all cases where the job is actually being rescheduled. As before, jobs which are already available with a past `ScheduledAt` will not be touched by this query so that they retain their place in line. [PR 211](https://github.com/riverqueue/river/pull/211).

Fixed

- Fixed a leadership re-election issue that was exposed by the fix in 199. Because we were internally using the same TTL for both an internal timer/ticker and the database update to set the new leader expiration time, a leader wasn't guaranteed to successfully re-elect itself even under normal operation. [PR 217](https://github.com/riverqueue/river/pull/217).