Upgrade to OTP 24. #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Erlang's crypto module has removed some deprecated functions in favour of a new API. This removes uses of the old functions which no longer work in OTP 24.
edennis
approved these changes
Apr 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"Erlang's crypto module has removed some deprecated functions in favor of a new API. This removes uses of the old functions which no longer work in OTP 24." - Original author.
OTP 24 comes with a lot of improvements, but also with a few deprecated functions being removed. With this PR we can safely upgrade all the dependent applications to the newest OTP version and get some of the nice compilation improvements from it.
See original PR: nsweeting#104