-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[deps] Update consul-template to v0.31.0 #16908
Conversation
8ba589f
to
abb0763
Compare
abb0763
to
b9a8edb
Compare
github.com/hashicorp/raft v1.3.11 | ||
github.com/hashicorp/raft-autopilot v0.1.6 | ||
github.com/hashicorp/raft-boltdb/v2 v2.2.2 | ||
github.com/hashicorp/serf v0.10.1 | ||
github.com/hashicorp/vault/api v1.9.1 | ||
github.com/hashicorp/vault/sdk v0.7.0 | ||
github.com/hashicorp/yamux v0.0.0-20211028200310-0bc27b27de87 | ||
github.com/hashicorp/yamux v0.1.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this intentional? Seems unrelated but idk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only commands I ran to make this PR were go get github.com/hashicorp/consul-template
and go mod tidy
. From what I can tell, it looks like a side-effect of the CT upgrade. CT v0.31.0 lists hashicorp/yamux v0.1.1 as an indirect dependency. I just did a check and yamux v0.1.1 does include the commit that we were linking to there.
I got identical behavior today, just redoing this against main (since I needed to rebase it anyway).
b9a8edb
to
d969c5c
Compare
No description provided.