-
Notifications
You must be signed in to change notification settings - Fork 56
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
Switch to warning/1 with updated build matrix #495
Conversation
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.
@sorentwo Since we are bumping the minimum required version of Elixir, should this be a major version release? Finally, the tests are failing, can you make sure they pass so that we can merge? Thanks! |
What can I do to help get this across goal line? |
@tjchambers Sorry, I totally forgot about this one. |
bump? |
2d613cd
to
66efe0c
Compare
@subzero10 @tjchambers, some extra work was required to get this passing cleanly. All set now! |
I think we can merge and push a release as soon as the conflicts are resolved. |
This swiitches from `Logger.warn` to `Logger.warning` because `warn` is deprecated and Elixir 1.15 shows a compile-time warning. The `warning` alternative was introduced in Elixir 1.11, so we're updating the build matrix to officially support 1.11 as the minimum Elixir version.
Only applications that aren't listed as depenencies, or their sub-dependencies, should be listed.
Config files are meant for applications, not libraries.
3ad847e
to
b9a2a57
Compare
@subzero10 Rebased. Once CI passes, I'll merge it. |
This swiitches from
Logger.warn
toLogger.warning
becausewarn
is deprecated, and the upcoming Elixir 1.15 shows a compile-time warning. Thewarning
alternative was introduced in Elixir 1.11, so we're officially updating the build matrix to support 1.11 as the minimum Elixir version.Closes #493