-
Notifications
You must be signed in to change notification settings - Fork 1
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 dependency com.vanniktech.maven.publish to v0.30.0 #16
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/com.vanniktech.maven.publish
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
January 6, 2024 21:27
d979d66
to
4ba7195
Compare
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.26.0
Update dependency com.vanniktech.maven.publish to v0.27.0
Jan 6, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.27.0
Update dependency com.vanniktech.maven.publish to v0.27.0 - autoclosed
Feb 2, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.27.0 - autoclosed
Update dependency com.vanniktech.maven.publish to v0.27.0
Feb 3, 2024
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
2 times, most recently
from
February 3, 2024 12:40
6018c31
to
44b549d
Compare
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.27.0
Update dependency com.vanniktech.maven.publish to v0.26.0
Feb 3, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.26.0
Update dependency com.vanniktech.maven.publish to v0.26.0 - autoclosed
Feb 3, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.26.0 - autoclosed
Update dependency com.vanniktech.maven.publish to v0.26.0
Feb 3, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.26.0
Update dependency com.vanniktech.maven.publish to v0.27.0
Feb 3, 2024
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
February 3, 2024 19:58
44b549d
to
3dbe2f6
Compare
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.27.0
Update dependency com.vanniktech.maven.publish to v0.27.0 - autoclosed
Feb 4, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.27.0 - autoclosed
Update dependency com.vanniktech.maven.publish to v0.27.0
Feb 4, 2024
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
February 4, 2024 09:36
3dbe2f6
to
5d786fd
Compare
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.27.0
Update dependency com.vanniktech.maven.publish to v0.28.0
Mar 13, 2024
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
March 13, 2024 01:52
5d786fd
to
77094f7
Compare
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
June 21, 2024 10:12
77094f7
to
8bbe584
Compare
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.28.0
Update dependency com.vanniktech.maven.publish to v0.29.0
Jun 21, 2024
renovate
bot
changed the title
Update dependency com.vanniktech.maven.publish to v0.29.0
Update dependency com.vanniktech.maven.publish to v0.30.0
Oct 13, 2024
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
October 13, 2024 12:53
8bbe584
to
38b7534
Compare
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
December 12, 2024 14:13
38b7534
to
85d0000
Compare
renovate
bot
force-pushed
the
renovate/com.vanniktech.maven.publish
branch
from
December 12, 2024 14:27
85d0000
to
6dd225d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.25.3
->0.30.0
Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.30.0
Compare Source
org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled
org.jetbrains.dokka
andorg.jetbrains.dokka-javadoc
org.jetbrains.dokka-android
pluginhttps
url inSONATYPE_HOST
Gradle propertyMinimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled
v0.29.0
Compare Source
configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)
overload that allows disabling sources and javadoc jars without having to use
the more granular
Platform
APIs.includes the sources jar.
afterEvaluate
anymore, making manual overrides easier.optimizations.
to the error message.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.28.0
Compare Source
this use the
CENTRAL_PORTAL
option when specifying the Sonatype host.release
variant if the project has an Android target and no variant was explicitlyspecified through the Kotlin Gradle DSL.
KotlinMultiplatform(...)
.closeAndReleaseRepository
task. UsereleaseRepository
, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.27.0
Compare Source
releaseRepository
releases a staging repository at the end of the buildand can be executed in the same build as the publishing task. This allows
having automatic releases without permanently enabling them.
publishToMavenCentral
as alias for runningpublishAllPublicationsToMavenCentralRepository
.publishAndReleaseToMavenCentral
as alias for running both of the above.coordinates(...)
and leave the others at their default value.Thanks to @sschuberth for the contribution.
java-test-fixture
projects being broken with Gradle 8.6.closeAndReleaseRepository
in favor ofreleaseRepository
.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
v0.26.0
Compare Source
configure(Platform)
from the main plugin to modifywhat is getting published. Check out the docs for more details
configureBasedOnAppliedPlugins
DSL method toallow applying the default
configure
logic of the main plugin.configure(Platform)
now validates that the required plugins areapplied (e.g. Android Gradle Plugin for Android projects).
times for Gradle plugin projects with more than one publication. Thanks to
@autonomousapps for the fix.
next release, because the Kotlin/JS plugin has been deprecated.
from
simpleJavadocJar
toplainJavadocJar
. Thanks to @sschuberth.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
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.
This PR was generated by Mend Renovate. View the repository job log.