# go: example.com/module@v0.0.0-20240830120000-abcdef123456: invalid pseudo-version: does not match version-control timestamp

- **ID:** `go/invalid-pseudo-version`
- **Domain:** go
- **Category:** build_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

A pseudo-version in go.mod has a timestamp or commit hash that does not correspond to any actual commit in the repository.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 1.13 | active | — | — |
| 1.14 | active | — | — |
| 1.15 | active | — | — |
| 1.16 | active | — | — |
| 1.17 | active | — | — |
| 1.18 | active | — | — |
| 1.19 | active | — | — |
| 1.20 | active | — | — |
| 1.21 | active | — | — |
| 1.22 | active | — | — |
| 1.23 | active | — | — |

## Workarounds

1. **Use 'go get' to fetch the correct pseudo-version from the repository** (90% success)
   ```
   go get example.com/module@master
   ```
2. **Run 'go mod tidy' to let Go resolve the correct version** (85% success)
   ```
   go mod tidy
   ```

## Dead Ends

- **Trying to use 'go mod edit -replace' with a different pseudo-version** — Any incorrect pseudo-version will trigger the same validation error. (80% fail)
- **Deleting the pseudo-version from go.mod manually** — Removing it without replacement will cause missing dependency errors. (70% fail)