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

Update plugin com.vanniktech.maven.publish to v0.25.3 #7

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.vanniktech.maven.publish 0.22.0 -> 0.25.3 age adoption passing confidence

Release Notes

vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)

v0.25.3

Compare Source

  • Gradle 8.2: Fix error for projects that use the java-test-fixtures plugin.
  • Fix issue for Kotlin Multiplatform projects when running tests and having signing enabled.

v0.25.2

Compare Source

  • Fix javadoc jar being empty when using dokka.

v0.25.1

Compare Source

  • Fix snapshot publishing being broken.

v0.25.0

Compare Source

  • 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.
  • Kotlin Multiplatform projects, blocked by KT-49933.

v0.24.0

Compare Source

  • 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.

v0.23.2

Compare Source

  • 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

v0.23.1

Compare Source

  • Also support publishing sources for the java-test-fixtures plugin in Kotlin/JVM projects.
  • Suppress Gradle warnings when publishing a project that uses java-test-fixtures.

v0.23.0

Compare Source

Updated docs can be found on the new website.

  • NEW: It is now possible to set group id, artifact id directly through the DSL
    mavenPublishing {
      coordinates("com.example", "library", "1.0.3")
    }
  • project.group and project.version will still be used as default values for group and version if the
    GROUP/VERSION_NAME Gradle properties do not exist and coordinates was not called, however there are 2
    behavior changes:
    • The GROUP and VERSION_NAME Gradle properties take precedence over project.group and project.version instead
      of being overwritten by them. If you need to define the properties but replace them for some projects,
      please use the new coordinates method instead.
    • The GROUP and VERSION_NAME Gradle properties will not be explicitly set as project.group and
      project.version anymore.
  • NEW: Added dropRepository task that will drop a Sonatype staging repository. It is possible to specify
    which repository to drop by adding a --repository parameter with the id of the staging repository that was
    printed during publish. If no repository is specified and there is only one staging repository, that one
    will be dropped.
  • Added workaround to also publish sources for the java-test-fixtures plugin
  • Fixed publishing Kotlin/JS projects with the base plugin.
  • Fixed that a POM configured through the DSL is incomplete when publishing Gradle plugins.
  • The minimum supported Gradle version has been increased to 7.3.
  • The plugin now requires using JDK 11+ to run Gradle.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update plugin com.vanniktech.maven.publish to v0.23.2 Update plugin com.vanniktech.maven.publish to v0.24.0 Jan 30, 2023
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from a463c5c to aa139c4 Compare January 30, 2023 06:55
@renovate renovate bot changed the title Update plugin com.vanniktech.maven.publish to v0.24.0 Update plugin com.vanniktech.maven.publish to v0.25.0 Mar 24, 2023
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from aa139c4 to d00bc07 Compare March 24, 2023 04:30
@renovate renovate bot changed the title Update plugin com.vanniktech.maven.publish to v0.25.0 Update plugin com.vanniktech.maven.publish to v0.25.1 Mar 24, 2023
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from d00bc07 to d14677a Compare March 24, 2023 15:34
@renovate renovate bot changed the title Update plugin com.vanniktech.maven.publish to v0.25.1 Update plugin com.vanniktech.maven.publish to v0.25.2 May 29, 2023
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from d14677a to 067531e Compare May 29, 2023 23:40
@renovate renovate bot changed the title Update plugin com.vanniktech.maven.publish to v0.25.2 Update plugin com.vanniktech.maven.publish to v0.25.3 Jul 2, 2023
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from 067531e to 042b0f2 Compare July 2, 2023 02:13
@jisungbin jisungbin closed this Sep 30, 2023
@jisungbin jisungbin deleted the renovate/com.vanniktech.maven.publish-0.x branch September 30, 2023 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant