-
Notifications
You must be signed in to change notification settings - Fork 693
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
Update cats-effect to 3.0.0 #2351
Conversation
Seems unrelated? |
I think the idea of having two modules is best. |
Yep, I will fix this, not related to anything. |
If you want to move out of draft I will merge. |
Cats-effect 3.0.0 final is planned for Sunday, 28th. I think it's reasonable to wait util then with merging. |
Sounds good.
…On Wed, 24 Mar 2021 at 11:18, Rafał Krzewski ***@***.***> wrote:
Cats-effect 3.0.0 final is planned for Sunday, 28th. I think it's
reasonable to wait util then with merging.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2351 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFVSGW22SUNXM43KJSZCFDTFIGEZANCNFSM4ZD7DRWA>
.
|
oops, I've added some some vscode and Metals files accidentally. Let me clean that up |
4330e24
to
9f3bca1
Compare
OK, it's ready to merge. |
I'll cut a 7.12 release with this later today. |
Cats-effect 3.0.0 release is coming up soon, so I thought a PR updating that dependency might be in order.
The ecosystem will OSS library ecosystem will probably upgrade quickly, but applications may lag behind for a while, so maybe creating a separate
elastic4s-effects-cats-2
module for providing compatibility with legacy cats-effect 2.x would be a good idea. Please let me know.