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

chore(kuma-cp) lock verison of ginkgo #756

Merged
merged 1 commit into from
May 21, 2020

Conversation

jakubdyszkiewicz
Copy link
Contributor

Summary

go get even without -u flag upgrades Ginkgo version in go.mod.
We don't want automatic upgrades of Ginkgo because it can bring dependencies that break build, therefore I'm locking the version.

Also installing Gomega as a part of dev/install/ginkgo is unnecessary.

@jakubdyszkiewicz jakubdyszkiewicz requested a review from a team May 21, 2020 11:25
@@ -107,6 +107,7 @@ PROTOC_VERSION := 3.6.1
PROTOC_PGV_VERSION := v0.3.0-java.0.20200311152155-ab56c3dd1cf9
GOLANG_PROTOBUF_VERSION := v1.3.2
GOLANGCI_LINT_VERSION := v1.26.0
GINKGO_VERSION := v1.12.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we lock the version to v1.12.2?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't because it upgrades github.com/golang/protobuf which breaks the project. I'll let it for a person who will be upgrading dependencies just like we said we will be doing monthly.

@jakubdyszkiewicz jakubdyszkiewicz merged commit eba0c38 into master May 21, 2020
@jakubdyszkiewicz jakubdyszkiewicz deleted the chore/remove-ginkgo-cli branch May 21, 2020 11:35
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.

None yet

3 participants