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

Provide the now required response object to the smtp exception #22268

Merged

Conversation

jrafanie
Copy link
Member

@jrafanie jrafanie commented Dec 5, 2022

mail gem 2.8.0 added ruby 3.1 support[1] which added net-smtp as an explicit gem dependency because it had recently become an extracted gem.

Previously, we used the ruby stdlib version, which was using gem version 0.1.0 in ruby 2.7.0 and 0.2.1 in ruby 3.0.0.

Starting with net-smtp 0.2.2, the Net::SMTPError types now require a response object [2] and an optional message. 🤷

[1] https://github.com/mikel/mail/pull/1472/files
[2] https://github.com/ruby/net-smtp/pull/26/files

mail gem 2.8.0 added ruby 3.1 support[1] which added net-smtp as an explicit gem
dependency because it had recently become an extracted gem.

Previously, we used the ruby stdlib version, which was using gem version 0.1.0
in ruby 2.7.0 and 0.2.1 in ruby 3.0.0.

Starting with net-smtp 0.2.2, the Net::SMTPError types now require a response
object [2] and an optional message. 🤷

[1] https://github.com/mikel/mail/pull/1472/files
[2] https://github.com/ruby/net-smtp/pull/26/files
@jrafanie
Copy link
Member Author

jrafanie commented Dec 5, 2022

I think this should be backported as far back as we'll pull in mail gem 2.8.0.

@Fryguy
Copy link
Member

Fryguy commented Dec 5, 2022

Seems like they broke semver?

@miq-bot
Copy link
Member

miq-bot commented Dec 5, 2022

Checked commit jrafanie@fdfbba0 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint
1 file checked, 0 offenses detected
Everything looks fine. 🍪

@agrare agrare merged commit bd821db into ManageIQ:master Dec 5, 2022
@Fryguy
Copy link
Member

Fryguy commented Dec 13, 2022

@jrafanie We are locked to 2.7.1 on oparin. Should we bump oparin to 2.8.0 and backport this? I'm concerned it might auto-update on us and we might forget to backport this otherwise.

@jrafanie jrafanie deleted the fix_required_response_arg_net_smtp_0_2_2 branch December 13, 2022 16:40
@jrafanie
Copy link
Member Author

@jrafanie We are locked to 2.7.1 on oparin. Should we bump oparin to 2.8.0 and backport this? I'm concerned it might auto-update on us and we might forget to backport this otherwise.

@Fryguy I'm comfortable with upgrading from 2.7.1 to 2.8.0 and pulling back this change to work with it. The changes don't look that significant and I'd rather find out now.

@jrafanie
Copy link
Member Author

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

Successfully merging this pull request may close these issues.

4 participants