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

chore(deps): update various version #19

Merged
merged 1 commit into from
Jan 11, 2023
Merged

Conversation

ckipp01
Copy link
Contributor

@ckipp01 ckipp01 commented Oct 24, 2022

This pr updates the following:

  • Scala 2.13 to the latest 2.13.10
  • mill-integrationtest to 0.6.1
  • mill.vcs.version to 0.3.0 and remove the stripping of v (done by default now)
  • Mill to latest 0.10.8 with a .mill-version file

This pr updates the following:

- Scala 2.13 to the latest 2.13.10
- mill-integrationtest to 0.6.1
- mill.vcs.version to 0.3.0 and remove the stripping of v (done by
  default now)
- Mill to latest 0.10.8 with a .mill-version file
@ckipp01
Copy link
Contributor Author

ckipp01 commented Oct 24, 2022

btw total aside, but I noticed that none of these were caught by Steward when they should have been. I created VirtusLab/scala-steward-repos#98 to follow-up.

override def artifactSuffix = s"_mill${millBinaryVersion(millVersion)}" + super.artifactSuffix()

def compileIvyDeps = Agg(ivy"com.lihaoyi::mill-scalalib:$millVersion")

def publishVersion: T[String] = VcsVersion.vcsState().format(tagModifier = _.dropWhile(_ == 'v'))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

So stripping the v is no longer necessary as this is done by default now. However, it got me wondering. I don't see any git tags associated with this repo. Are you just manually tagging via GitHub or something or how are you releasing?

Copy link
Owner

Choose a reason for hiding this comment

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

Hi @ckipp01 I've not been so involved with this repo recently but as far as I know we're just using git tags for releasing on tag pushes
image

Copy link
Collaborator

Choose a reason for hiding this comment

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

Sorry I missed this PR. I did not quiet understand the next steps. Is publishVersion defined by default without v now?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @ckipp01 I've not been so involved with this repo recently but as far as I know we're just using git tags for releasing on tag pushes

Yup, this was my bad, I hadn't fetched everything upstream and was only dealing with my fork. Just ignore that part.

Sorry I missed this PR. I did not quiet understand the next steps. Is publishVersion defined by default without v now?

Well the logic we had here was stripping the v which as of 0.2.0 is done by default.

@ckipp01
Copy link
Contributor Author

ckipp01 commented Jan 11, 2023

Thanks for the follow-up on this. Just let me know what else you need to get this across the board. More importantly, can you also look at #18.

@joan38 joan38 merged commit 8f18079 into DavidGregory084:main Jan 11, 2023
@joan38
Copy link
Collaborator

joan38 commented Jan 11, 2023

Thanks @ckipp01 !
0.3.2 on it's way

@ckipp01 ckipp01 deleted the mill branch January 11, 2023 14:57
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.

3 participants