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

Require Ruby >= 2.5, add Psych 4 support, and get CI green #1478

Merged
merged 10 commits into from
Apr 21, 2022

Conversation

deivid-rodriguez
Copy link
Contributor

I unified the changes from #1472 and #1476 intended to get a base green CI line.

I tweaked #1476 to use safe loading by default but still fully support Psych 3.

Link to green actions run on my fork: https://github.com/deivid-rodriguez/mail/runs/6076144108?check_suite_focus=true.

README.md Outdated Show resolved Hide resolved
lib/mail.rb Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
deivid-rodriguez and others added 7 commits April 19, 2022 14:48
So that it doesn't timeout but fails in a standard way.
The standard `ruby/setup-ruby` action has all rubies that we need and
has the added advantages of builtin gem caching and providing an up to
date version of TruffleRuby, which behaves better.
It's failing consistently, and doesn't seem mail's fault.
Provides a clear guidance on what versions of Ruby mail supports now and into the future.
@deivid-rodriguez deivid-rodriguez force-pushed the drop-old-rubies-support branch from aebf484 to 670bb87 Compare April 19, 2022 12:52
@deivid-rodriguez deivid-rodriguez force-pushed the drop-old-rubies-support branch from 670bb87 to 100a4f2 Compare April 20, 2022 07:31
@mikel
Copy link
Owner

mikel commented Apr 20, 2022

Awesome work @deivid-rodriguez - could @voxik or @simi please do one review through this and give it a thumbs up? This is a pretty major change and I would love another couple of eyes on it. Then I'll merge and we'll release Mail 2.8.0.rc1 into a stable branch

@voxik
Copy link
Contributor

voxik commented Apr 20, 2022

I mainly care about a20fdd5, which looks good. I also like the clarification of the support policy. Other than that, I can't see anything worrisome.

@deivid-rodriguez
Copy link
Contributor Author

Thanks for having a look @voxik 👍. I'll rebase and get #1472 ready as soon as this is merged 💪.

@jeremy
Copy link
Collaborator

jeremy commented Apr 20, 2022 via email

@deivid-rodriguez
Copy link
Contributor Author

In my experience, the support policy of extracted stdlibs is not really established, but they are usually more aggressive than this when it comes to dropping support for old rubies. For example, net-imap 0.2.2 supports ruby 2.5+, while net-imap 0.2.3 (the latest version) supports ruby 2.6+.

@mikel mikel merged commit b9fa30a into mikel:master Apr 21, 2022
@mikel
Copy link
Owner

mikel commented Apr 21, 2022

Looks good to me @deivid-rodriguez @voxik - let's get 1472 under control now. Then I'll release 2.8.0.rc1

mikel added a commit that referenced this pull request Apr 21, 2022
Adding update from PR #1478
@deivid-rodriguez deivid-rodriguez deleted the drop-old-rubies-support branch April 21, 2022 11:49
require 'mail/version_specific/ruby_1_8'
RubyVer = Ruby18
end

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm afraid these are public constants that are broadly referenced, so removal will cause surprising downstream breakage: RubyVer, Ruby18, Ruby19

A deprecation cycle would be sensible.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also Ruby18, given that we're dropping Ruby 1.8 support? The link you provided does not show any meaningful results in the first pages for me.

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.

5 participants