Update plugin com.vanniktech.maven.publish to v0.25.3 #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.22.0
->0.25.3
Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.25.3
Compare Source
java-test-fixtures
plugin.v0.25.2
Compare Source
v0.25.1
Compare Source
v0.25.0
Compare Source
createStagingRepository
task now uses the worker API which allows the project to builtin parallel to the creation of the staging repository.
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
constructorwith a
sourcesJar
parameter has been deprecated.java-test-fixtures
projectscom.gradle.plugin-publish
1.0.0 and 1.1.0com.gradle.plugin-publish
1.0.0common
sources jar for multiplatform projects will only containthe 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:
v0.24.0
Compare Source
v0.23.2
Compare Source
The plugin will also fallback to any staging profile that has a matching prefix with the group id.
java-test-fixtures
projects,project.group
and
project.version
are now being set again for those projects. #490v0.23.1
Compare Source
java-test-fixtures
plugin in Kotlin/JVM projects.java-test-fixtures
.v0.23.0
Compare Source
Updated docs can be found on the new website.
project.group
andproject.version
will still be used as default values for group and version if theGROUP
/VERSION_NAME
Gradle properties do not exist andcoordinates
was not called, however there are 2behavior changes:
GROUP
andVERSION_NAME
Gradle properties take precedence overproject.group
andproject.version
insteadof being overwritten by them. If you need to define the properties but replace them for some projects,
please use the new
coordinates
method instead.GROUP
andVERSION_NAME
Gradle properties will not be explicitly set asproject.group
andproject.version
anymore.dropRepository
task that will drop a Sonatype staging repository. It is possible to specifywhich repository to drop by adding a
--repository
parameter with the id of the staging repository that wasprinted during
publish
. If no repository is specified and there is only one staging repository, that onewill be dropped.
java-test-fixtures
pluginConfiguration
📅 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.
This PR has been generated by Mend Renovate. View repository job log here.