Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump com.vanniktech.maven.publish.base from 0.25.3 to 0.27.0 (#176)
Bumps [com.vanniktech.maven.publish.base](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.25.3 to 0.27.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases">com.vanniktech.maven.publish.base's releases</a>.</em></p> <blockquote> <h2>0.27.0</h2> <ul> <li>Added new publishing related tasks <ul> <li><code>releaseRepository</code> releases a staging repository at the end of the build and can be executed in the same build as the publishing task. This allows having automatic releases without permanently enabling them.</li> <li><code>publishToMavenCentral</code> as alias for running <code>publishAllPublicationsToMavenCentralRepository</code>.</li> <li><code>publishAndReleaseToMavenCentral</code> as alias for running both of the above.</li> <li>For more information <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/central/#publishing-releases">checkout the docs</a>.</li> </ul> </li> <li>It is now possible to only pass a subset of the parameters to <code>coordinates(...)</code> and leave the others at their default value. Thanks to <a href="https://github.com/sschuberth"><code>@sschuberth</code></a> for the contribution.</li> <li>Fixed <code>java-test-fixture</code> projects being broken with Gradle 8.6.</li> <li>Deprecated <code>closeAndReleaseRepository</code> in favor of <code>releaseRepository</code>.</li> </ul> <h4>Minimum supported versions</h4> <ul> <li>JDK 11</li> <li>Gradle 7.6</li> <li>Android Gradle Plugin 7.4.0</li> <li>Kotlin Gradle Plugin 1.8.20</li> </ul> <h4>Compatibility tested up to</h4> <ul> <li>JDK 21</li> <li>Gradle 8.5</li> <li>Gradle 8.6-rc-1</li> <li>Android Gradle Plugin 8.2.1</li> <li>Android Gradle Plugin 8.3.0-beta01</li> <li>Android Gradle Plugin 8.4.0-alpha03</li> <li>Kotlin Gradle Plugin 1.9.22</li> <li>Kotlin Gradle Plugin 2.0.0-Beta2</li> </ul> <h4>Configuration cache status</h4> <p>When using <strong>Gradle 8.1</strong> or newer configuration cache is generally supported.</p> <p>Exceptions to that are:</p> <ul> <li>Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue <a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/22779">#22779</a>](<a href="https://redirect.github.com/gradle/gradle/issues/22779">gradle/gradle#22779</a>).</li> <li>Dokka does not support configuration cache</li> </ul> <h2>0.26.0</h2> <ul> <li>It's now supported to call <code>configure(Platform)</code> from the main plugin to modify what is getting published. <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/what/">Check out the docs for more details</a></li> <li>The base plugin now has a <code>configureBasedOnAppliedPlugins</code> DSL method to allow applying the default <code>configure</code> logic of the main plugin.</li> <li>Calling <code>configure(Platform)</code> now validates that the required plugins are applied (e.g. Android Gradle Plugin for Android projects).</li> <li>It's now possible to disable source publishing for KMP projects.</li> <li>Fixed an issue which would cause the javadoc jar task to be registered multiple times for Gradle plugin projects with more than one publication. Thanks to</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </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.maven.publish.base's changelog</a>.</em></p> <blockquote> <h2>0.27.0 <em>(2024-01-06)</em></h2> <ul> <li>Added new publishing related tasks <ul> <li><code>releaseRepository</code> releases a staging repository at the end of the build and can be executed in the same build as the publishing task. This allows having automatic releases without permanently enabling them.</li> <li><code>publishToMavenCentral</code> as alias for running <code>publishAllPublicationsToMavenCentralRepository</code>.</li> <li><code>publishAndReleaseToMavenCentral</code> as alias for running both of the above.</li> <li>For more information <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/central/#publishing-releases">checkout the docs</a>.</li> </ul> </li> <li>It is now possible to only pass a subset of the parameters to <code>coordinates(...)</code> and leave the others at their default value. Thanks to <a href="https://github.com/sschuberth"><code>@sschuberth</code></a> for the contribution.</li> <li>Fixed <code>java-test-fixture</code> projects being broken with Gradle 8.6.</li> <li>Deprecated <code>closeAndReleaseRepository</code> in favor of <code>releaseRepository</code>.</li> </ul> <h4>Minimum supported versions</h4> <ul> <li>JDK 11</li> <li>Gradle 7.6</li> <li>Android Gradle Plugin 7.4.0</li> <li>Kotlin Gradle Plugin 1.8.20</li> </ul> <h4>Compatibility tested up to</h4> <ul> <li>JDK 21</li> <li>Gradle 8.5</li> <li>Gradle 8.6-rc-1</li> <li>Android Gradle Plugin 8.2.1</li> <li>Android Gradle Plugin 8.3.0-beta01</li> <li>Android Gradle Plugin 8.4.0-alpha03</li> <li>Kotlin Gradle Plugin 1.9.22</li> <li>Kotlin Gradle Plugin 2.0.0-Beta2</li> </ul> <h4>Configuration cache status</h4> <p>When using <strong>Gradle 8.1</strong> or newer configuration cache is generally supported.</p> <p>Exceptions to that are:</p> <ul> <li>Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue <a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/22779">#22779</a>](<a href="https://redirect.github.com/gradle/gradle/issues/22779">gradle/gradle#22779</a>).</li> <li>Dokka does not support configuration cache</li> </ul> <h2>0.26.0 <em>(2023-12-19)</em></h2> <ul> <li>It's now supported to call <code>configure(Platform)</code> from the main plugin to modify what is getting published. <a href="https://vanniktech.github.io/gradle-maven-publish-plugin/what/">Check out the docs for more details</a></li> <li>The base plugin now has a <code>configureBasedOnAppliedPlugins</code> DSL method to allow applying the default <code>configure</code> logic of the main plugin.</li> <li>Calling <code>configure(Platform)</code> now validates that the required plugins are applied (e.g. Android Gradle Plugin for Android projects).</li> <li>It's now possible to disable source publishing for KMP projects.</li> <li>Fixed an issue which would cause the javadoc jar task to be registered multiple</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/0139cc82597460126ed81b8b33e4ba7960c55db2"><code>0139cc8</code></a> use 0.27.0-rc2</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/78d4a65f4387638dcb2f67d5b2d28eab262f92ab"><code>78d4a65</code></a> use 0.27.0-rc2</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/55c7960f7c73b47ae528bbc03dc23eae00e95521"><code>55c7960</code></a> fix stagingRepositoryId check (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/703">#703</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/21de5204b072db939f16285daf4a20a31b6b957b"><code>21de520</code></a> use new tasks</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/2c51b870baf1999ad5d9ebb33b1398ecd7858705"><code>2c51b87</code></a> Update to 0.27.0-rc1</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/66b8efe51a0e13758a489dbc2ea655bf0db33091"><code>66b8efe</code></a> Changelog for 0.27.0 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/702">#702</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/793614305266316b581285423dfa903715709670"><code>7936143</code></a> add new release task (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/699">#699</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/4fb8a9f6d3b4b0eeab1731c2029bec8307e4510d"><code>4fb8a9f</code></a> fix(deps): update dependency com.android.tools.build:gradle to v8.2.1 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/701">#701</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/eed76ce1163fc4c6cedd78d67cb14e1819c03d4b"><code>eed76ce</code></a> chore(deps): update plugin buildconfig to v5.3.2 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/700">#700</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/8558785f912362c2942a109a3b03ade755f3cef3"><code>8558785</code></a> always close, release and drop from build service (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/698">#698</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/compare/0.25.3...0.27.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.vanniktech.maven.publish.base&package-manager=gradle&previous-version=0.25.3&new-version=0.27.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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information