-
Notifications
You must be signed in to change notification settings - Fork 938
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
Add Ruby 3.1 support #1472
Add Ruby 3.1 support #1472
Conversation
I was wondering why the truffleruby job gets cancelled, and found https://github.com/deivid-rodriguez/mail/actions/runs/1853944108
So it seems because of the rather low And potentially the CI could (later) run outside Docker now that it doesn't require such ancient Ruby versions like 1.8, which would make the CI faster as well. |
da1de3d
to
cc5dd2c
Compare
24cb453
to
30d1819
Compare
This is now green and I'm happy with it! |
Is there anything else TBD before merging that to the gem itself? Thanks for the great job! |
A maintainer of this gem needs to review the PR. From my side it's ready. |
@deivid-rodriguez FWIW, I think there is no need to depend on the io-wait gem, is there? |
316d8c9
to
508f432
Compare
Let's get #1476 passing CI and merged first, then we can rebase this and move forward @deivid-rodriguez @simi and @voxik |
🙏 time to rebase @deivid-rodriguez |
508f432
to
3d577d0
Compare
The default RubyGems version on Ruby 2.5 has issues with it.
3d577d0
to
6182cf0
Compare
The released version of `truffleruby` does not work with old versions of Bundler. However, it's not possible to specify a custom version of Bundler in truffleruby, because the `ruby/setup-ruby` will ignore that in the case of `truffleruby-22.0` (the current release) That's in my opinion an issue with `ruby/setup-ruby` because it should respect user's choice when it's explicit. But it's not possible to change that because it was an explicit choice of that library. So as an alternative solution, use `truffleruby-head`, which apparently does not have the issue.
5c24652
to
63a749c
Compare
This should be ready now! |
Mit Ruby 3.1 ist u.a. 'net-smtp' aus den Standardabhängigkeiten entfallen. 'mail' benötigt diese Abhängigkeit und löst diese jedoch erst ab Version 2.8.0 selbst auf (mikel/mail#1472), das bisher noch nicht veröffentlicht wurde (nur als RC1).
@mikel Please do the final release of 2.8.0? This issue is causing a problem for many people as you can see in all the references above. |
* Update Ruby 3.1.2 Mit Ruby 3.1 ist u.a. 'net-smtp' aus den Standardabhängigkeiten entfallen. 'mail' benötigt diese Abhängigkeit und löst diese jedoch erst ab Version 2.8.0 selbst auf (mikel/mail#1472), das bisher noch nicht veröffentlicht wurde (nur als RC1). Co-authored-by: Niels Bennke <[email protected]>
Is there a stable release with this out yet or just the rc? |
Folks, I recently upgraded to |
Little has changed, unfortunately. Previously to the rc release, you needed to include Hopefully @mikel will release the final version soon. |
@mikel any update on this? |
Ruby 3.1 removed net-smtp from stdlib which causes a problem when Rails 6 loads the mail gem [1]. Rails 7 has a fix for this [2]. I expect it won't be too long until we drop support for Rails 6 and can remove this. [1]: mikel/mail#1472 [2]: rails/rails@cb44df7
Ruby 3.1 removed net-smtp from stdlib which causes a problem when Rails 6 loads the mail gem [1]. Rails 7 has a fix for this [2]. I expect it won't be too long until we drop support for Rails 6 and can remove this. [1]: mikel/mail#1472 [2]: rails/rails@cb44df7
Ruby 3.1 removed net-smtp from stdlib which causes a problem when Rails 6 loads the mail gem [1]. Rails 7 has a fix for this [2]. I expect it won't be too long until we drop support for Rails 6 and can remove this. [1]: mikel/mail#1472 [2]: rails/rails@cb44df7
…d false accordig to issue mikel/mail#1472
* matrix: teamcapybara/capybara#2468 * `nokogiri 🤷 but there's no version constraint anyways * `net-*`: mikel/mail#1472 It's been quite a while so these seem safe to drop
* matrix: teamcapybara/capybara#2468 * `nokogiri 🤷 but there's no version constraint anyways * `net-*`: mikel/mail#1472 It's been quite a while so these seem safe to drop
* Remove some explicit dependencies from the gemfile * matrix: teamcapybara/capybara#2468 * `nokogiri 🤷 but there's no version constraint anyways * `net-*`: mikel/mail#1472 It's been quite a while so these seem safe to drop * Run different rails versions tests in parallel Ditch appraisals while we're at it
No description provided.