Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump com.vanniktech:gradle-maven-publish-plugin from 0.18.0 to 0.25.2 #172

Open
wants to merge 1 commit into
base: 3.x
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 17, 2023

Bumps com.vanniktech:gradle-maven-publish-plugin from 0.18.0 to 0.25.2.

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin's releases.

0.25.2

  • Fix javadoc jar being empty when using dokka.

0.25.1

  • Fix snapshot publishing being broken.

0.25.0

  • The createStagingRepository task now uses the worker API which allows the project to built in parallel to the creation of the staging repository.
  • Fix incompatibility with Kotlin 1.8.20-Beta for Kotlin/JS projects. The Kotlin/JS plugin is now taking care of creating the sources jar on its own. Because of this the base plugin won't allow disabling sources jar creation for Kotlin/JS projects anymore starting with 1.8.20. The KotlinJs constructor with a sourcesJar parameter has been deprecated.
  • Fix incompatibility with Gradle 8.1 for java-test-fixtures projects
  • Fix incompatibility with com.gradle.plugin-publish 1.0.0 and 1.1.0
  • New minimum supported versions:
    • Gradle 7.4
    • Android Gradle Plugin 7.3.0
    • Kotlin Gradle Plugin 1.7.0
    • com.gradle.plugin-publish 1.0.0
  • Note: Starting with Kotlin 1.8.20-Beta the common sources jar for multiplatform projects will only contain the sources of the common source set instead of containing the sources from all source sets.

Configuration cache status

Configuration cache is supported starting with Gradle 7.6+ except for:

  • Builds with enabled signing, will be resolved in Gradle 8.1.
  • Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](gradle/gradle#22779).
  • Kotlin Multiplatform projects, blocked by KT-49933.

0.24.0

  • Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org.
  • Support adjusting timeouts for Sonatype related requests and operations. See docs
  • Internal change on how the sources jar is created.

0.23.2

  • Fix signing when using Gradle 8.0.
  • 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.
  • As a workaround for an issue in Gradle that causes invalid module metadata for java-test-fixtures projects, project.group and project.version are now being set again for those projects. #490

0.23.1

Changelog

... (truncated)

Changelog

Sourced from com.vanniktech:gradle-maven-publish-plugin's changelog.

0.25.2 (2023-04-16)

  • Fix javadoc jar being empty when using dokka.

0.25.1 (2023-03-24)

  • Fix snapshot publishing being broken.

0.25.0 (2023-03-23)

  • The createStagingRepository task now uses the worker API which allows the project to built in parallel to the creation of the staging repository.
  • Fix incompatibility with Kotlin 1.8.20-Beta for Kotlin/JS projects. The Kotlin/JS plugin is now taking care of creating the sources jar on its own. Because of this the base plugin won't allow disabling sources jar creation for Kotlin/JS projects anymore starting with 1.8.20. The KotlinJs constructor with a sourcesJar parameter has been deprecated.
  • Fix incompatibility with Gradle 8.1 for java-test-fixtures projects
  • Fix incompatibility with com.gradle.plugin-publish 1.0.0 and 1.1.0
  • New minimum supported versions:
    • Gradle 7.4
    • Android Gradle Plugin 7.3.0
    • Kotlin Gradle Plugin 1.7.0
    • com.gradle.plugin-publish 1.0.0
  • Note: Starting with Kotlin 1.8.20-Beta the common sources jar for multiplatform projects will only contain the sources of the common source set instead of containing the sources from all source sets.

Configuration cache status

Configuration cache is supported starting with Gradle 7.6+ except for:

  • Builds with enabled signing, will be resolved in Gradle 8.1.
  • Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](gradle/gradle#22779).
  • Kotlin Multiplatform projects, blocked by KT-49933.

0.24.0 (2023-01-29)

  • Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org.
  • Support adjusting timeouts for Sonatype related requests and operations. See docs
  • Internal change on how the sources jar is created.

0.23.2 (2023-01-17)

  • Fix signing when using Gradle 8.0.
  • 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.
  • As a workaround for an issue in Gradle that causes invalid module metadata for java-test-fixtures projects, project.group and project.version are now being set again for those projects. #490

... (truncated)

Commits

Dependabot compatibility score

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 commands and options

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)

Bumps [com.vanniktech:gradle-maven-publish-plugin](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.18.0 to 0.25.2.
- [Release notes](https://github.com/vanniktech/gradle-maven-publish-plugin/releases)
- [Changelog](https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md)
- [Commits](vanniktech/gradle-maven-publish-plugin@0.18.0...0.25.2)

---
updated-dependencies:
- dependency-name: com.vanniktech:gradle-maven-publish-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants