Bump the go-dependencies group across 2 directories with 9 updates

[dependabot]

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

[bgentry]

🤖 Codex review: Approved after dependency security and compatibility review.

Upgrade

• River module set: v0.45.0 → v0.47.0 (river, riverdriver, riverpgxv5, riversqlite, rivershared, and rivertype)
• River Pro module set: v0.28.0 → v0.30.1 (riverpro, driver, riverpropgxv5, and riverprosqlite)
• Reviewed head: 361b5d6a90c9ae1eec81c07de6ca4d249ca8834b

Security review

• Downloaded and compared every old/new module archive. The PR's module and go.mod checksums match the published artifacts; the public modules verify through the Go checksum database, and the private River Pro artifacts match the exact organization release tags file-for-file through the configured River proxy.
• The imported archives contain no production-source changes. Their deltas are aligned River/River Pro module references plus release notes; the corresponding verified release commits contain the documented Postgres-listener and SQLite CLI work in sibling modules with focused tests.
• No third-party graph churn, replace/exclude change, pseudo-version, generated or vendored code, binary asset, cgo/assembly, new initialization side effect, credential access, process execution, telemetry, or downloader was introduced. The official Go vulnerability database lists no advisory for the upgraded module paths, and River has no published repository security advisory.

Compatibility verification

• go mod download and go mod verify in both affected modules — passed
• go mod tidy in both affected modules — passed with no diff
• golangci-lint run --fix ./... across all three repository Go modules — passed with no diff
• CGO_ENABLED=0 go build ./... across all three repository Go modules — passed
• make test/race against PostgreSQL 18 — passed across all three repository Go modules
• CI Go lint and the full Go 1.26/1.27 × PostgreSQL 16/17/18 matrix — passed

Residual risk

• The riverproui image workflow stopped before its build because Dependabot's workflow identity could not assume the AWS cache role. The equivalent Pro Go binary build and race-tested packages pass locally; this is an infrastructure authorization limitation rather than a dependency compatibility failure.
• River Pro is private and intentionally outside the public Go checksum database; exact checksums were verified against the configured proxy and exact tagged source.