Update changelog to prepare for 0.0.4 release

[brandur]

Add the changes in #29 and #30 to the changelog so that we can cut a
0.0.4 release. For brevity and to keep signal high, I didn't include
changes that came in which aren't user facing.

[brandur]

Just added backticks to these things.

[bgentry]

Should we get in the habit of bumping the riverpgxv5 version here for each release? I think it affects which version gets pulled down on go get github.com/riverqueue/river.

[brandur]

Should we get in the habit of bumping the riverpgxv5 version here for each release? I think it affects which version gets pulled down on go get github.com/riverqueue/river.

Sure. What's the order of operations there exactly? Do you have to bump it before you cut the release tag? (Presumably leaving the repo in a temporarily invalid state.)

[bgentry]

Yes, I think that’s correct. We should probably get in the habit of a “release prep” PR like this one which includes changelog entries and the version bump, then tag both modules immediately after merge.

[brandur]

Yes, I think that’s correct. We should probably get in the habit of a “release prep” PR like this one which includes changelog entries and the version bump, then tag both modules immediately after merge.

Alright, I'll give it a shot.

Also added changelog entries for the minor docs change and reindexer disable.

[brandur]

Build passed even with the manually tweaked go.mod pointing to a non-existent version ... surprisingly.

[bgentry]

Build passed even with the manually tweaked go.mod pointing to a non-existent version ... surprisingly.

Yeah, builds within this module use the local replace directive in the go.mod, whereas that's ignored outside this module/repo. So you can point to an invalid version number in here and it just gets ignored because it's importing directly from the filesystem anyway.