You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DO NOT submit tickets without first using the latest version of Golang, clearing your local golang package cache, and re-building mockery using the latest Golang version and the latest version of mockery. Please provide evidence this has been done in your issue. Failure to provide this evidence will likely result in your issue being closed.
Description
Mockery Version > v2.9.4 is using a module called github.com/spf13/viper < v1.16.0 which contains a module called ectd. The version 3.5.1 to 3.5.6 of etcd package includes critical vulnerability CVE-2021-28235. Upgrade to Viper package using etcd > v3.5.6.
Mockery Version
Version > v2.9.4
Golang Version
go 1.21
NOTE: Please upgrade to the latest golang version before submitting tickets!
Installation Method
Binary Distribution
Docker
brew
go install
Other: [specify]
Steps to Reproduce
[First Step]
[Second Step]
[etc]
Expected Behavior
Would be nice to upgrade viper to version > v.1.15.0
Actual Behavior
[what actually happened]
The text was updated successfully, but these errors were encountered:
PLEASE READ
DO NOT submit tickets without first using the latest version of Golang, clearing your local golang package cache, and re-building mockery using the latest Golang version and the latest version of mockery. Please provide evidence this has been done in your issue. Failure to provide this evidence will likely result in your issue being closed.
Description
Mockery Version > v2.9.4 is using a module called github.com/spf13/viper < v1.16.0 which contains a module called ectd. The version 3.5.1 to 3.5.6 of etcd package includes critical vulnerability CVE-2021-28235. Upgrade to Viper package using etcd > v3.5.6.
Mockery Version
Version > v2.9.4
Golang Version
go 1.21
Installation Method
Steps to Reproduce
Expected Behavior
Would be nice to upgrade viper to version > v.1.15.0
Actual Behavior
[what actually happened]
The text was updated successfully, but these errors were encountered: