# ambiguous import: found package example.com/foo in multiple modules:
	example.com/foo v1.0.0
	example.com/foo/v2 v2.1.0

- **ID:** `go/ambiguous-import-path`
- **Domain:** go
- **Category:** module_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

Both a v1 and v2 module provide the same import path, usually because the v2 module failed to include /v2 in its module path or was forked incorrectly.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 1.16+ | active | — | — |
| 1.21+ | active | — | — |

## Workarounds

1. **** (85% success)
   ```
   go mod edit -exclude=example.com/foo@v1.0.0
go mod tidy
   ```
2. **** (80% success)
   ```
   go mod edit -replace=example.com/foo=example.com/foo/v2@v2.1.0
go mod tidy
   ```

## Dead Ends

- **** — ambiguity persists; go refuses to pick one (95% fail)
- **** — does not resolve which module owns the path (90% fail)
- **** — the module still declares the colliding path (70% fail)