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

Update mill-scalalib to 289f9e3aa3f5014a5c64319da8e6ab993947ade2-0-289f9e #1550

Closed
wants to merge 3 commits into from
Closed

Update mill-scalalib to 289f9e3aa3f5014a5c64319da8e6ab993947ade2-0-289f9e #1550

wants to merge 3 commits into from

Conversation

scala-steward
Copy link
Contributor

Updates com.lihaoyi:mill-scalalib from 0.6.3 to 289f9e3aa3f5014a5c64319da8e6ab993947ade2-0-289f9e.

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 = "com.lihaoyi", artifactId = "mill-scalalib" } ]

labels: library-update

@lefou
Copy link
Member

lefou commented Aug 26, 2020

Just to provide some context: It is right to not merge this PR. The suggested upgrade is a result of an automated release process in mill which tried to infer the nearest release version from the last tag found in git history. Due to the default checkout process on Travis-CI only the last 50 git history entries were present which resulted in these awkward version numbers once we had more than 50 commits after the last tagged release.

@fthomas
Copy link
Member

fthomas commented Sep 2, 2020

Thanks for the info, @lefou. Something similar also happened in this repository and could happen again if there is no new release 500 commits after the last one: 2d603bf :-)

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.

3 participants