Skip to content

build(deps): Bump Vanniktech Maven Publish plugin to 0.35.0#1335

Merged
runningcode merged 1 commit into
mainfrom
no/update-vanniktech-maven-publish-0.36.0
Jun 24, 2026
Merged

build(deps): Bump Vanniktech Maven Publish plugin to 0.35.0#1335
runningcode merged 1 commit into
mainfrom
no/update-vanniktech-maven-publish-0.36.0

Conversation

@runningcode

Copy link
Copy Markdown
Contributor

Bumps the Vanniktech Maven Publish plugin from 0.27.0 to 0.35.0 in gradle/libs.versions.toml, and regenerates plugin-build's SHA-256 verification metadata (required by STRICT-mode dependency locking whenever a plugin-build dependency changes).

Why not 0.36.0?

0.36.0 (the current latest) raises the minimum Kotlin Gradle Plugin version to 2.2.0:

Make sure the Kotlin version 2.2.0 or newer is applied.

This repo is still on Kotlin 2.1.21, so applying 0.36.0 fails the build. 0.35.0 is the highest release compatible with the current Kotlin version. We can move to 0.36.0 once the Kotlin upgrade lands.

Bump from 0.27.0 to 0.35.0 and regenerate plugin-build's SHA-256
verification metadata, which STRICT-mode locking requires when a
plugin-build dependency changes.

0.36.0 is the current latest, but it raises the minimum Kotlin Gradle
Plugin version to 2.2.0; this repo is still on Kotlin 2.1.21, so 0.35.0
is the highest compatible release.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
@runningcode
runningcode force-pushed the no/update-vanniktech-maven-publish-0.36.0 branch from 4045c64 to 94dc1eb Compare June 23, 2026 13:53
@runningcode
runningcode merged commit 837663f into main Jun 24, 2026
23 checks passed
@runningcode
runningcode deleted the no/update-vanniktech-maven-publish-0.36.0 branch June 24, 2026 07:45
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.

2 participants