Setting version to 1.4.1 #284
Conversation
0xRoch
force-pushed
the
version-release-1-4-1
branch
from
a10fcf8 to
380cdd8
Compare
0xRoch
force-pushed
the
version-release-1-4-1
branch
from
380cdd8 to
1795a85
Compare
|
This is extremely puzzling, this commit is not available in master branch 👀 neither is the artifact published on maven central. Was the master branch reverted back? |
|
@D-Roch what went wrong? You shouldn't change the version by hand. Versions are updated during release process. |
|
@gslowikowski yes I reverted it sorry about that. Do you have time to do a sbt release ? |
|
@gslowikowski - I normally publish the Gradle plugin to Sonatype under the org.scoverage group. I could probably create a release build and publish it if you're too busy? |
|
@maiflai I will try to release. Probably first existing 1.4.1 release and tag should be deleted. |
|
@gslowikowski @D-Roch fwiw, the revert of master branch was not done correctly, ideally I'd expect the commits in https://github.com/scoverage/scalac-scoverage-plugin/commits/6c29fb19b3ff042983de8d87a6ecb21557a7c854 match the commits in https://github.com/scoverage/scalac-scoverage-plugin/commits/master, but the top few don't |
No description provided.