A couple minor changelog additions for 0.0.16 release

A few short changelog entries for the next release to include:

* #137
* #138
* #140

CHANGELOG.md

@@ -7,12 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.16] - 2024-01-06
+
+### Changed
+
+- Calls to `Stop` error if the client hasn't been started yet. [PR #138](https://github.com/riverqueue/river/pull/138).
+
+### Fixed
+
+- Fix typo in leadership resignation query to ensure faster new leader takeover. [PR #134](https://github.com/riverqueue/river/pull/134).
+- Elector now uses the same `log/slog` instance configured by its parent client. [PR #137](https://github.com/riverqueue/river/pull/137).
+- Notifier now uses the same `log/slog` instance configured by its parent client. [PR #140](https://github.com/riverqueue/river/pull/140).
+
 ## [0.0.15] - 2023-12-21
 
 ### Fixed
 
 - Ensure `ScheduledAt` is respected on `InsertManyTx`. [PR #121](https://github.com/riverqueue/river/pull/121).
-- Fix typo in leadership resignation query to ensure faster new leader takeover. [PR #134](https://github.com/riverqueue/river/pull/134).
 
 ## [0.0.14] - 2023-12-13
 

docs/development.md

@@ -25,9 +25,8 @@ queries. After changing an sqlc `.sql` file, generate Go with:
 
 ## Releasing a new version
 
-1. First, prepare a PR with a `CHANGELOG.md` update describing the changes, and update the root `go.mod` to point to the `riverpgxv5` version that is about to be released.
-2. Merge the above PR.
-3. Next, fetch the repo locally, bump dependency versions, tag each submodule, and push those tags:
+1. Prepare a PR with a `CHANGELOG.md` update describing the changes. Have it reviewed and merged.
+2. Next, fetch the repo locally, bump dependency versions, tag each submodule, and push those tags:
 
 ```shell
 git checkout master && git pull --rebase
@@ -52,4 +51,4 @@ If updates to River dependencies _are_ required, then a two-phase update is nece
 1. Release River dependencies with an initial version (e.g. `v0.0.14`).
 2. From `./cmd/river`, `go get` to upgrade to the version from (1), run `go mod tidy`, then tag it with the same version (e.g. `v0.0.14`).
 
-    The main `v0.0.14` tag and `cmd/river/v0.0.14` will point to different commits, but this is tolerable.
+    The main `v0.0.14` tag and `cmd/river/v0.0.14` will point to different commits, but this is tolerable.