From 848158d9a0ea1858eb1b843689050c1b658aebb0 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 15 Feb 2023 09:30:06 -0800
Subject: [PATCH] Bump com.vanniktech:gradle-maven-publish-plugin from 0.22.0
 to 0.24.0 (#4511)

Summary:
Bumps [com.vanniktech:gradle-maven-publish-plugin](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.22.0 to 0.24.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases">com.vanniktech:gradle-maven-publish-plugin's releases</a>.</em></p>
<blockquote>
<h2>0.24.0</h2>
<ul>
<li>Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org.</li>
<li>Support adjusting timeouts for Sonatype related requests and operations. <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/central/#timeouts">See docs</a></li>
<li>Internal change on how the sources jar is created.</li>
</ul>
<h2>0.23.2</h2>
<ul>
<li>Fix signing when using Gradle 8.0.</li>
<li>Finding a matching staging profile in Sonatype is more lenient. If there is just one that one will always be used.
The plugin will also fallback to any staging profile that has a matching prefix with the group id.</li>
<li>As a workaround for an issue in Gradle that causes invalid module metadata for <code>java-test-fixtures</code> projects, <code>project.group</code>
and <code>project.version</code> are now being set again for those projects. <a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/pull/490">https://github.com/facebook/flipper/issues/490</a></li>
</ul>
<h2>0.23.1</h2>
<p><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md#version-0231-2022-12-30">Changelog</a></p>
<h2>0.23.0</h2>
<p><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md#version-0230-2022-12-29">Changelog</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md">com.vanniktech:gradle-maven-publish-plugin's changelog</a>.</em></p>
<blockquote>
<h2>0.24.0 <em>(2023-01-29)</em></h2>
<ul>
<li>Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org.</li>
<li>Support adjusting timeouts for Sonatype related requests and operations. <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/central/#timeouts">See docs</a></li>
<li>Internal change on how the sources jar is created.</li>
</ul>
<h2>0.23.2 <em>(2023-01-17)</em></h2>
<ul>
<li>Fix signing when using Gradle 8.0.</li>
<li>Finding a matching staging profile in Sonatype is more lenient. If there is just one that one will always be used.
The plugin will also fallback to any staging profile that has a matching prefix with the group id.</li>
<li>As a workaround for an issue in Gradle that causes invalid module metadata for <code>java-test-fixtures</code> projects, <code>project.group</code>
and <code>project.version</code> are now being set again for those projects. <a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/pull/490">https://github.com/facebook/flipper/issues/490</a></li>
</ul>
<h2>0.23.1 <em>(2022-12-30)</em></h2>
<ul>
<li>Also support publishing sources for the <code>java-test-fixtures</code> plugin in Kotlin/JVM projects.</li>
<li>Suppress Gradle warnings when publishing a project that uses <code>java-test-fixtures</code>.</li>
</ul>
<h2>0.23.0 <em>(2022-12-29)</em></h2>
<p>Updated docs can be found on <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/">the new website</a>.</p>
<ul>
<li><strong>NEW</strong>: It is now possible to set group id, artifact id directly through the DSL
<pre lang="groovy"><code>mavenPublishing {
  coordinates(&quot;com.example&quot;, &quot;library&quot;, &quot;1.0.3&quot;)
}
</code></pre>
</li>
<li><code>project.group</code> and <code>project.version</code> will still be used as default values for group and version if the
<code>GROUP</code>/<code>VERSION_NAME</code> Gradle properties do not exist and <code>coordinates</code> was not called, however there are 2
<strong>behavior changes</strong>:
<ul>
<li>The <code>GROUP</code> and <code>VERSION_NAME</code> Gradle properties take precedence over <code>project.group</code> and <code>project.version</code> instead
of being overwritten by them. If you need to define the properties but replace them for some projects,
please use the new <code>coordinates</code> method instead.</li>
<li>The <code>GROUP</code> and <code>VERSION_NAME</code> Gradle properties will not be explicitly set as <code>project.group</code> and
<code>project.version</code> anymore.</li>
</ul>
</li>
<li><strong>NEW</strong>: Added <code>dropRepository</code> task that will drop a Sonatype staging repository. It is possible to specify
which repository to drop by adding a <code>--repository</code> parameter with the id of the staging repository that was
printed during <code>publish</code>. If no repository is specified and there is only one staging repository, that one
will be dropped.</li>
<li>Added workaround to also publish sources for the <code>java-test-fixtures</code> plugin</li>
<li>Fixed publishing Kotlin/JS projects with the base plugin.</li>
<li>Fixed that a POM configured through the DSL is incomplete when publishing Gradle plugins.</li>
<li>The minimum supported Gradle version has been increased to 7.3.</li>
<li>The plugin now requires using JDK 11+ to run Gradle.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/7faa441d3af45f6aa84b03384062d3fd2bdb526c"><code>7faa441</code></a> Prepare changelog for release 0.24.0.</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/95f5b4eb7927553403b2120f6f5028bc60093d10"><code>95f5b4e</code></a> make timeouts configurable (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/508">https://github.com/facebook/flipper/issues/508</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/4b4302027a71061fe8e38cedda329c07e8576db2"><code>4b43020</code></a> replace custom sources jar task (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/507">https://github.com/facebook/flipper/issues/507</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/744db566a10d81a9a48b995e84c544403be513da"><code>744db56</code></a> Update dependency org.jlleitschuh.gradle:ktlint-gradle to v11.1.0 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/506">https://github.com/facebook/flipper/issues/506</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/f041faa59d4a95596ee514790174936db7b344d5"><code>f041faa</code></a> Open up SonatypeHost (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/504">https://github.com/facebook/flipper/issues/504</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/9300a2be9cd63b3616646fbc6f33173b36f9b8ef"><code>9300a2b</code></a> Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.23.2 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/501">https://github.com/facebook/flipper/issues/501</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/8f3edf1e75dbb0081913d523545a3eed5c2eebf4"><code>8f3edf1</code></a> Update CHANGELOG for 0.23.2.</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/b944e0d46a92fea4125a315b880006bf0ac64987"><code>b944e0d</code></a> test against Gradle 8.0-rc-2 and AGP 8.0.0-alpha11 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/499">https://github.com/facebook/flipper/issues/499</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/93a21886fad618a2d185361d8472a051192c7993"><code>93a2188</code></a> make finding a staging profile more lenient (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/498">https://github.com/facebook/flipper/issues/498</a>)</li>
<li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/6686704e1dcd29a80325c65f6dcad01fad19cb9b"><code>6686704</code></a> Update dependency com.android.tools.build:gradle to v7.4.0 (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/495">https://github.com/facebook/flipper/issues/495</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/compare/0.22.0...0.24.0">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.vanniktech:gradle-maven-publish-plugin&package-manager=gradle&previous-version=0.22.0&new-version=0.24.0)](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/4511

Reviewed By: ivanmisuno

Differential Revision: D43303376

Pulled By: passy

fbshipit-source-id: f434a912d246bb7e916d0afb2ee9cf3a5d8bd8d4
---
 build.gradle | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/build.gradle b/build.gradle
index a15e2aca0..706bdce4b 100644
--- a/build.gradle
+++ b/build.gradle
@@ -12,7 +12,7 @@ buildscript {
     }
     dependencies {
         classpath 'com.android.tools.build:gradle:7.3.0'
-        classpath 'com.vanniktech:gradle-maven-publish-plugin:0.22.0'
+        classpath 'com.vanniktech:gradle-maven-publish-plugin:0.24.0'
         classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$KOTLIN_VERSION"
         classpath "org.jetbrains.dokka:dokka-gradle-plugin:1.7.20"
         classpath "org.jetbrains.kotlin:kotlin-serialization:$KOTLIN_VERSION"