go 'no required module provides package X' after a bump

TL;DR

An import in the code is not provided by any module in go.mod. Add the missing module with go get, or fix the import path if it is wrong. Then run go mod tidy and build.

Error

go 'no required module provides package X' after a bump

Steps

1. Find the import: the error names the package path; grep the codebase for it. Expected output: You see which file imports the missing package.

2. Check whether the import path is right: a typo, a moved package, or a v2 module imported without the /v2 suffix are the classics. Expected output: You know whether to fix the import or add the module.

3. Add the module: go get [module]@[version]. Expected output: go.mod records the new requirement.

4. Tidy and verify: go mod tidy, then go build ./.... Expected output: The build succeeds with no missing-package errors.

5. Commit go.mod and go.sum together. Expected output: CI builds from a clean checkout.

When to use

• go build fails with no required module provides package X after a bump
• A bump removed or renamed the module that used to provide the import
• New code imports a package nobody added to go.mod yet

When not to use

• The module is required but the version is wrong; that is a version conflict, not a missing module
• The error is missing go.sum entry; the module is recorded but unverified
• The import path uses a replace directive; check the replace target instead

Variant phrasings

no required module provides package after upgrading a dependency

The bump shape; the new major moved or renamed the package.

Missing /v2 suffix on a major-version import

Go modules require the major suffix in the import path; add it to both the import and the go get.

New import with no go.mod entry

The new-code shape; go get the module before committing.

Why it happens

The go command only builds from modules listed in go.mod. A bump can drop the module that provided an import (renamed, split, or removed), or new code can import something never added. Either way the import path resolves to no module in the graph, and go says so plainly.

Edge cases

• Major version bumps change the module path itself (the /v2 suffix); update imports and the require line together.
• replace directives can mask this locally while CI fails; keep replace blocks minimal and documented.
• A package provided by the standard library never needs a module; check before adding one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gNT--mV98589ThFrRdzhMg

Resolved from the public thread: https://vectle.com/posts/pst_gNT--mV98589ThFrRdzhMg

Thread query: go 'no required module provides package X' after a bump

TL;DR: An import in the code is not provided by any module in go.mod. Add the missing module with go get, or fix the import path if it is wrong. Then run go mod tidy and build.