Skip to content

[v3.2] Require mail >= 2.8.0.rc1 for Ruby 3.1 support#4735

Closed
tvdeyen wants to merge 1 commit intosolidusio:v3.2from
tvdeyen:3.2-ruby-3.1-fixes
Closed

[v3.2] Require mail >= 2.8.0.rc1 for Ruby 3.1 support#4735
tvdeyen wants to merge 1 commit intosolidusio:v3.2from
tvdeyen:3.2-ruby-3.1-fixes

Conversation

@tvdeyen
Copy link
Copy Markdown
Member

@tvdeyen tvdeyen commented Nov 23, 2022

Same as #4734 but for v3.2

@kennyadsl
Copy link
Copy Markdown
Member

@tvdeyen you don't need to create this PR, when #4734 will be merged with the needs-backport-3.2 label, this same PR will be created on the v3.2 branch.

Ruby 3.1 removed net-smtp, net-imap and net-pop from
standardlib and extracted them into independent gems.

The mail gem >= 2.8.0.rc1 added them to their dependencies.
Since we require the mail gem in core.rb:17 we need to
add the mail gem as dependency and need to make sure
it is the Ruby 3.1 compatible version as we support
Ruby 3.1
@tvdeyen tvdeyen changed the title [v3.2] Require mail >= 2.8 for Ruby 3.1 support [v3.2] Require mail >= 2.8.0.rc1 for Ruby 3.1 support Nov 23, 2022
@tvdeyen
Copy link
Copy Markdown
Member Author

tvdeyen commented Nov 23, 2022

@tvdeyen you don't need to create this PR, when #4734 will be merged with the needs-backport-3.2 label, this same PR will be created on the v3.2 branch.

@kennyadsl wow! nice. Should I close this PR now?

@kennyadsl
Copy link
Copy Markdown
Member

Yep, please see #4678.

@tvdeyen tvdeyen closed this Nov 23, 2022
@tvdeyen tvdeyen deleted the 3.2-ruby-3.1-fixes branch November 23, 2022 11:26
@tvdeyen
Copy link
Copy Markdown
Member Author

tvdeyen commented Nov 23, 2022

This is very helpful for contributors! ❤️

@kennyadsl
Copy link
Copy Markdown
Member

Maybe we should be more clear somehow that it's not required anymore (most of the times) to create these backport PRs.

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.

2 participants