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

Use a proper Mill release instead of a hash version #1613

Merged
merged 1 commit into from
Sep 12, 2020

Conversation

fthomas
Copy link
Member

@fthomas fthomas commented Sep 11, 2020

We switched to a hash version in #1551 but that switch wasn't intentional. Such PRs are now prevented by #1552.

@codecov
Copy link

codecov bot commented Sep 11, 2020

Codecov Report

Merging #1613 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1613   +/-   ##
=======================================
  Coverage   70.29%   70.29%           
=======================================
  Files         113      113           
  Lines        1781     1781           
  Branches       52       52           
=======================================
  Hits         1252     1252           
  Misses        529      529           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c999c8...3967f55. Read the comment docs.

@fthomas fthomas merged commit b2ab3bd into master Sep 12, 2020
@fthomas fthomas added this to the 0.7.0 milestone Sep 12, 2020
@fthomas fthomas deleted the topic/use-proper-mill-release branch September 13, 2020 07:32
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.

1 participant