Bump gradle-maven-publish-plugin from 0.19.0 to 0.20.0 (#3795)
Summary: Bumps [gradle-maven-publish-plugin](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.19.0 to 0.20.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases">gradle-maven-publish-plugin's releases</a>.</em></p> <blockquote> <h2>0.20.0</h2> <p><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md#version-0200-2022-06-02">Changelog</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md">gradle-maven-publish-plugin's changelog</a>.</em></p> <blockquote> <h2>Version 0.20.0 <em>(2022-06-02)</em></h2> <p><strong>Upcoming behavior change</strong></p> <p>In the next release after this the <code>com.vanniktech.maven.publish</code> will stop adding Maven Central (Sonatype OSS) as a publishing target and will not enable GPG signing by default. If you are curretly relying on this behavior the plugin will print a warning during configuration phase. To continue publishing to maven central and signing artifacts either add this to your build files:</p> <pre lang="gradle"><code>mavenPublishing { publishToMavenCentral() // use publishToMavenCentral("S01") for publishing through s01.oss.sonatype.org enableReleaseSigning() } </code></pre> <p>or the following to your <code>gradle.properties</code>:</p> <pre lang="gradle"><code>SONATYPE_HOST=DEFAULT # SONATYPE_HOST=S01 for publishing through s01.oss.sonatype.org RELEASE_SIGNING_ENABLED=true </code></pre> <p>The base plugin is unaffected by these changes because it already has this behavior.</p> <p><strong>Deprecation</strong></p> <p>The old <code>mavenPublish</code> extension has been deprecated.</p> <p>If you were using it to set <code>sonatypeHost</code> to <code>S01</code> use</p> <pre lang="gradle"><code>mavenPublishing { publishToMavenCentral("S01") } </code></pre> <p>instead or add <code>SONATYPE_HOST=S01</code> to your gradle.properties.</p> <p>If <code>sonatypeHost</code> was used to disable adding Maven Central as a publishing target add <code>SONATYPE_HOST=</code> until 0.21.0 is out and this becomes the default behavior.</p> <p>If you set <code>releaseSigningEnabled</code> to false add <code>RELEASE_SIGNING_ENABLED=false</code> to your gradle.properties until 0.21.0 is out and this becomes the default behavior.</p> <p><strong>New</strong></p> <p>Added support to set the following pom values through properties (thanks to <a href="https://github.com/jaredsburrows"><code>@jaredsburrows</code></a> for the contribution)</p> <ul> <li><code>POM_ISSUE_SYSTEM</code> sets <code>issueManagement.system</code></li> <li><code>POM_ISSUE_URL</code> sets <code>issueManagement.url</code></li> <li><code>POM_DEVELOPER_EMAIL</code> sets <code>developer.email</code></li> </ul> <p><strong>Fixed</strong></p> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="300595008c"><code>3005950</code></a> Prepare for release 0.20.0.</li> <li><a href="643bea069f"><code>643bea0</code></a> update changelog for 0.20.0 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/352">https://github.com/facebook/flipper/issues/352</a>)</li> <li><a href="582f0d4fb9"><code>582f0d4</code></a> fix Kotlin MPP project not being configured when Android plugin is present (#...</li> <li><a href="399b0f9b23"><code>399b0f9</code></a> fix legacy Android setup in mpp projects (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/350">https://github.com/facebook/flipper/issues/350</a>)</li> <li><a href="c8dd40ce5a"><code>c8dd40c</code></a> deprecate old mavenPublish extension (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/340">https://github.com/facebook/flipper/issues/340</a>)</li> <li><a href="8e1f12d659"><code>8e1f12d</code></a> fix error message when no repo is found (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/337">https://github.com/facebook/flipper/issues/337</a>)</li> <li><a href="6134aa06ef"><code>6134aa0</code></a> Bump actions/setup-java from 2 to 3 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/348">https://github.com/facebook/flipper/issues/348</a>)</li> <li><a href="e6fee7ceba"><code>e6fee7c</code></a> Bump actions/checkout from 2 to 3 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/349">https://github.com/facebook/flipper/issues/349</a>)</li> <li><a href="951262297f"><code>9512622</code></a> Create dependabot.yml (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/347">https://github.com/facebook/flipper/issues/347</a>)</li> <li><a href="d03e6e586b"><code>d03e6e5</code></a> Support more POM properties (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/345">https://github.com/facebook/flipper/issues/345</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/compare/0.19.0...0.20.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `dependabot rebase` will rebase this PR - `dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `dependabot merge` will merge this PR after your CI passes on it - `dependabot squash and merge` will squash and merge this PR after your CI passes on it - `dependabot cancel merge` will cancel a previously requested merge and block automerging - `dependabot reopen` will reopen this PR if it is closed - `dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Pull Request resolved: https://github.com/facebook/flipper/pull/3795 Reviewed By: lawrencelomax Differential Revision: D37070881 Pulled By: passy fbshipit-source-id: df3df877a5dd182a289608e624099e32f687e076
This commit is contained in:
committed by
Facebook GitHub Bot
parent
b25a212890
commit
d54944346c
@@ -12,7 +12,7 @@ buildscript {
|
||||
}
|
||||
dependencies {
|
||||
classpath 'com.android.tools.build:gradle:7.0.4'
|
||||
classpath 'com.vanniktech:gradle-maven-publish-plugin:0.19.0'
|
||||
classpath 'com.vanniktech:gradle-maven-publish-plugin:0.20.0'
|
||||
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$KOTLIN_VERSION"
|
||||
classpath "org.jetbrains.dokka:dokka-gradle-plugin:1.6.21"
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user