CI Run Link: https://github.com/coder/coder/actions/runs/20256286255
Failing Job: nightly-gauntlet / test-go-pg (windows-2022)
Completed: 2025-12-16T04:21:04Z (same day and within minutes of Slack alert)
Run attempt: 1

Commit Info:

• SHA: 871ed128aad8b515ef6c88764398c824bc01eb80
• Author: Asher
• Message: chore: update azure certs (#21265)
• Link: coder/coder@871ed12

Error evidence (from job logs):

go: github.com/coder/boundary@v1.0.1-0.20250925154134-55a44f2a7945: invalid pseudo-version: preceding tag (v1.0.0) not found
##[error]Process completed with exit code 1.

What actually failed

• Tests did not run on Windows because go list/test dependency resolution failed while fetching github.com/coder/boundary.
• Datadog upload shows Uploaded 0 files (no tests executed).
• macOS job for the same run succeeded; Windows job is the sole failure (not a matrix cancellation artifact).

Root cause classification: Code change / dependency resolution

• The repository references github.com/coder/boundary at:
  • go.mod: github.com/coder/boundary v1.0.1-0.20250925154134-55a44f2a7945
• The Go toolchain reports the pseudo-version is invalid because the preceding tag (v1.0.0) cannot be found for that commit/tag topology. This typically occurs if the expected base tag was removed/renamed, or the commit is not reachable from the expected tag lineage.
• This is not a test flake, race, panic, or infra issue.

Precise assignment analysis (commands/evidence used)

• Located dependency pin: go.mod contains github.com/coder/boundary v1.0.1-0.20250925154134-55a44f2a7945.
• Code references/ownership context:
  • boundary integration files:
    • cli/exp_boundary.go
    • cli/exp_boundary_test.go
  • Recent owner who introduced boundary CLI: commit ada20d26917a — "feat: implement coder exp boundary subcommand (#19771)" (2025-09-30).
• Assigning to component owner @dannykopping for triage; if a different boundary maintainer is more appropriate, please reassign.

Duplicate detection (comprehensive):

• Searched coder/internal for: "invalid pseudo-version", "pseudo-version", "github.com/coder/boundary"; no matches found (open or recently closed).
• Searched for Nightly gauntlet Windows dependency failures — no related issue for this root cause.

Suggested next steps:

1. Inspect github.com/coder/boundary tags around commit 55a44f2a7945 (timestamp 2025-09-25) and restore/create the expected base tag (v1.0.0 or adjust to a valid version lineage), or
2. Update coder/coder go.mod to a valid boundary version (prefer a release tag) and run the matrix to confirm Windows resolution succeeds.
3. Consider adding a CI safeguard that periodically validates module resolution on Windows to catch tag lineage issues earlier.

Reproduction:

• On a Windows environment: go mod download / go test ./... from main should reproduce the same pseudo-version error.

Why this is not a flake:

• Deterministic dependency resolution error; no tests ran; reproducible via module fetch.