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

Upgrade eetcd to v0.5.0 #12994

Merged
merged 1 commit into from
Dec 23, 2024
Merged

Upgrade eetcd to v0.5.0 #12994

merged 1 commit into from
Dec 23, 2024

Conversation

ansd
Copy link
Member

@ansd ansd commented Dec 23, 2024

eetcd v0.5.0 is compatible with OTP 27 and depends on gun 2.1.0

eetcd v0.5.0 is compatible with OTP 27 and depends on gun 2.1.0
@ansd ansd added this to the 4.1.0 milestone Dec 23, 2024
@mergify mergify bot added the make label Dec 23, 2024
@ansd
Copy link
Member Author

ansd commented Dec 23, 2024

FTR: Unless we see any breakage of eetcd 0.3.6 on v4.0.x with OTP 27, @michaelklishin and I decided to keep using eetcd 0.3.6 including gun 1.3.3 on v4.0.x.

In other words, for now, we backport neither this PR nor #12980 because the risks of TLS config breakage of backporting #12980 to v4.0.x is higher than the benefits of using the latest eectd and gun versions.

@michaelklishin michaelklishin merged commit 94e4397 into main Dec 23, 2024
271 checks passed
@michaelklishin michaelklishin deleted the upgrade-eetcd branch December 23, 2024 23:07
@michaelklishin
Copy link
Member

Correct. But over time we may choose to backport this change because for the series under [longer] commercial support it might make sense one day to upgrade even those dependencies that require certain internal changes. But right now, there aren't specific reasons for backporting that we know of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants