8000 Update scala3-library, ... to 3.1.0 by scala-steward · Pull Request #307 · typelevel/cats-time · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update scala3-library, ... to 3.1.0 #307

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 18, 2021
Merged

Update scala3-library, ... to 3.1.0 #307

merged 1 commit into from
Oct 18, 2021

Conversation

scala-steward
Copy link
Contributor

Updates

from 3.0.2 to 3.1.0.
GitHub Release Notes - Version Diff - Version Diff

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

Ignore future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-minor

@cquiroz cquiroz merged commit 951826d into typelevel:main Oct 18, 2021
@lukoyanov
Copy link
Member

@cquiroz

Have you seen this thread?
https://twitter.com/SethTisue/status/1450260785762947076

Will this merge affect library users on scala 3.0?

@cquiroz
Copy link
Contributor
cquiroz commented Oct 19, 2021

Good point, I didn't know about it. I guess it won't be a problem until we do a next release?

@lukoyanov
Copy link
Member

Yes, it will not affect anyone until we release the next version, but it looks like we have to come up with a solution to support both scala 3 and scala 3.1 users.

@cquiroz
Copy link
Contributor
cquiroz commented Oct 19, 2021

Right, if there is a typelevel policy about it we could follow it
Coming from scala.js which has had this policy for a while I'm not too worried

@cquiroz
Copy link
Contributor
cquiroz commented Oct 19, 2021

but if there is a workable solution, for sure we could adopt it

@rossabaker
Copy link
Member

There's no Typelevel policy, but I just posted a PR to revert jawn-fs2. I'm treating Scala 3 like Java: use the latest patch of the earliest breaking release that works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@scala-steward @lukoyanov @cquiroz @rossabaker
0