Prepare version 0.12.0

vanniktech · Jul 7, 2020 · 79b940f · 79b940f
1 parent 60f7bf7
commit 79b940f
Show file tree

Hide file tree

Showing 3 changed files with 19 additions and 7 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,7 +1,17 @@
 # Change Log
 
-Version 0.12.0 *(In development)*
----------------------------------
+Version 0.12.0 *(2020-07-07)*
+-----------------------------
+
+- only create one closeAndRelease task, add new property for the profile [\#148](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/148) ([gabrielittner](https://github.com/gabrielittner))
+- fix AndroidJavadocs task [\#147](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/147) ([gabrielittner](https://github.com/gabrielittner))
+- don't fail on unknown plugins [\#142](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/142) ([gabrielittner](https://github.com/gabrielittner))
+- Use POM\_INCEPTION\_YEAR gradle property [\#140](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/140) ([benjamin-bader](https://github.com/benjamin-bader))
+- cleanup after legacy was removed [\#136](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/136) ([gabrielittner](https://github.com/gabrielittner))
+- remove legacy mode [\#135](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/135) ([gabrielittner](https://github.com/gabrielittner))
+- wait for transitioning to be false before releasing [\#133](https://github.com/vanniktech/gradle-maven-publish-plugin/pull/133) ([gabrielittner](https://github.com/gabrielittner))
+
+Kudos to [gabrielittner](https://github.com/gabrielittner).
 
 Version 0.11.1 *(2020-03-30)*
 -----------------------------

diff --git a/README.md b/README.md
@@ -14,7 +14,7 @@ buildscript {
     mavenCentral()
   }
   dependencies {
-    classpath 'com.vanniktech:gradle-maven-publish-plugin:0.11.1'
+    classpath 'com.vanniktech:gradle-maven-publish-plugin:0.12.0'
   }
 }
 
@@ -158,9 +158,9 @@ mavenPublish {
     }
 }
 ```
-The `stagingProfile` set here is either the same as your group id or a simpler version of it. When you are publishing a 
-library with `com.example.mylibrary` as group then it would either be the same or just `com.example`. You can find it 
-by looking at your [Sonatype staging profiles](https://oss.sonatype.org/#stagingProfiles) in the name and repo target 
+The `stagingProfile` set here is either the same as your group id or a simpler version of it. When you are publishing a
+library with `com.example.mylibrary` as group then it would either be the same or just `com.example`. You can find it
+by looking at your [Sonatype staging profiles](https://oss.sonatype.org/#stagingProfiles) in the name and repo target
 columns.
 
 This will create a `closeAndReleaseRepository` task that you can call after `uploadArchives`:

diff --git a/gradle.properties b/gradle.properties
@@ -1,5 +1,5 @@
 GROUP=com.vanniktech
-VERSION_NAME=0.12.0-SNAPSHOT
+VERSION_NAME=0.12.0
 
 POM_ARTIFACT_ID=gradle-maven-publish-plugin
 POM_NAME=Gradle Maven Publish Plugin
@@ -20,3 +20,5 @@ POM_LICENCE_DIST=repo
 POM_DEVELOPER_ID=vanniktech
 POM_DEVELOPER_NAME=Niklas Baudy
 POM_DEVELOPER_URL=https://github.com/vanniktech/
+
+systemProp.org.gradle.internal.publish.checksums.insecure=true