Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove github.com/stretchr/testify dependency #112

Closed
wants to merge 1 commit into from

Conversation

bflad
Copy link
Contributor

@bflad bflad commented May 26, 2022

Given this Go module underpins many others, it should likely try to minimize dependencies where possible. This removes the testify dependency by converting the unit testing logic to local testing helpers. Happy to adjust this change or take another approach.


Additional Context

Ultimately this is reference to GHSA-hp87-p4gw-j4gq, where gopkg.in/yaml.v3 recently had a CVE filed against it. That Go module is a dependency of this one via testify, according to go mod why -m gopkg.in/yaml.v3:

github.com/hashicorp/go-hclog
github.com/hashicorp/go-hclog.test
github.com/stretchr/testify/assert
gopkg.in/yaml.v3

Indirectly referencing a YAML handling module seems less than ideal for a logging system, especially if it is only for some testing helpers.

References

Given this Go module underpins many others, it should try to minimize dependencies. This removes the testify dependency by converting the unit testing logic to local testing helpers.
@bflad bflad force-pushed the bflad-remove-testify-dependency branch from fd0a796 to 1e251ac Compare May 27, 2022 15:08
@bflad
Copy link
Contributor Author

bflad commented May 27, 2022

Rebased on top of #113

bflad added a commit that referenced this pull request Jun 6, 2022
Reference: GHSA-hp87-p4gw-j4gq
Reference: #112

Updates the github.com/stretchr/testify dependency, which in turn updates the gopkg.in/yaml.v3 dependency. Updated via:

```shell
go get github.com/stretchr/testify@v1.7.2
go mod tidy
```
@evanphx
Copy link
Contributor

evanphx commented Jul 25, 2022

This was fixed in #114 instead.

@evanphx evanphx closed this Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants