chores: retract module github.com/stretchrcom/testify

Open Beginner friendly
#1,892 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go
Domain
release

Research direction

Start by reading go.mod and the issue's linked golang/go request about pkg.go.dev. Confirm the historical releases and the alternate module path described in the issue, then make the module metadata retract that path and verify that the invalid alternate module is no longer presented as intended.

Written by the indexing model from the issue text.

Description

internal/cleanup

Retract Go module github.com/stretchrcom/testify which is visible on pkg.go.dev (I'm not linking here on purpose) with releases v1.1.1 to v1.2.2.

What happened?

The stretch GitHub organization was at some point in history named stretchrcom. As a result, the Testify repository is also accessible via a redirect from that organization. And Google seems to have fetch the repository under the github.com/stretchrcom/testify and it is currently (2026-05-15) visible at https://pkg.go.dev/github.com/stretchrcom/testify with releases v1.1.1 to v1.2.2. New releases stopped to appear with that path when go.mod has been added in c45a1382af909f3ed0abc3b8d8e59e6db48ed9d8 published from release v1.3.0.

What to do?

The official package path has always been github.com/stretchr/testify. Nobody has ever imported this project under github.com/stretchrcom/testify. So it makes no sense to have github.com/stretchrcom/testify visible on pkg.go.dev.

So let's clean this invalid alternate module.

I've filled a request for pkg.go.dev: https://github.com/golang/go/issues/79420

Dominant language
Go
Stars
26.2k
Forks
1.9k
Avg merge
2d 4h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

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

More from stretchr/testify

All issues in stretchr/testify

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.