Difficulty updating submodule versions

Open

#1,043 opened on Sep 18, 2025 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: Go
Stars: 5.7k
Forks: 179
Avg merge: 15h 43m
Merged PRs (30d): 13

Description

I'm currently on version v0.23.1

When I try to update I get the following output:

❯ go get -u github.com/riverqueue/river
go: upgraded github.com/riverqueue/river v0.23.1 => v0.25.0
go: upgraded github.com/riverqueue/river/riverdriver v0.23.1 => v0.25.0
go: upgraded github.com/riverqueue/river/riverdriver/riverpgxv5 v0.23.1 => v0.25.0
go: upgraded github.com/riverqueue/river/rivershared v0.23.1 => v0.25.0
go: upgraded github.com/riverqueue/river/rivertype v0.23.1 => v0.25.0
go: upgraded github.com/tidwall/match v1.1.1 => v1.2.0
go: upgraded golang.org/x/mod v0.27.0 => v0.28.0

After when I run go mod tidy

❯ go mod tidy
go: finding module for package github.com/riverqueue/river/internal/util/dbutil
go: github.com/riverqueue/river/cmd/river imports
        github.com/riverqueue/river/cmd/river/rivercli imports
        github.com/riverqueue/river/riverdriver/riversqlite imports
        github.com/riverqueue/river/internal/util/dbutil: module github.com/riverqueue/river@latest found (v0.25.0), but does not contain package github.com/riverqueue/river/internal/util/dbutil
make: *** [tidy] Error 1

Any ideas how to solve it?

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Reproduce the failure with go get -u github.com/riverqueue/river followed by go mod tidy. Trace the imports from cmd/river through cmd/river/rivercli and riverdriver/riversqlite to internal/util/dbutil, and inspect the repository's tidy target. Done means the documented update path completes without the missing-package error.

Written by the indexing model from the issue text.

Assessment

Tech stack: go
Domain: build-system
Issue type: Bug
Difficulty: 3/5
Estimated time: 1-2 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 45/100