Update plugin com.gradleup.nmcp.aggregation to v1.6.1#1241
Open
renovate[bot] wants to merge 1 commit into
Open
Update plugin com.gradleup.nmcp.aggregation to v1.6.1#1241renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
loosebazooka
approved these changes
Jul 7, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
1.4.0→1.6.1Release Notes
gradleup/nmcp (com.gradleup.nmcp.aggregation)
v1.6.12026-07-01
Restores some checksums:
maven-metadata.md5,maven-metadata.sha1(becausemavenoutputs a scary warning without them).sha512checksums (because Gradle uses them to validate caches contents)All in all, nmcp now publishes
.md5,.sha1,.sha512for all files except for signature files (.asc) where no checksums are required.Long term, I'd love to drop the
.md5and.sha1checksums. That would require both maven and Sonatype to stop requesting them.Many thanks to @marcphilipp and @leonard84 for helping me navigate this issue 💙
v1.6.02026-06-21
Nmcp 1.6.0 stop publishing the following checksums:
.asc.md5,.asc.sha1,.asc.sha256,.asc.sha512).sha256,.sha512)maven-metadatachecksums (for local publishing,maven-metadata.xmlis never sent to Central Portal)You can send the checksums by setting
publishAllChecksumsv1.5.02026-04-30
Nmcp 1.5.0 adds
nmcpPublishDeployment()to publish an existing deployment to the Central Portal (#251):Many thanks @marcphilipp for the contribution!
v1.4.42026-01-24
Nmcp 1.4.4 retries more aggressively when Sonatype is flaky, and makes it more explicit that
publishAllProjectsProbablyBreakingProjectIsolation()is still OK to use if you don't mind about project isolation.v1.4.32026-01-02
Version 1.4.3 adds
NmcpAggregationExtension.allowDuplicateProjectNames(#239) as an escape hatch for the duplicate name check (#233)v1.4.22025-12-31
Version 1.4.2 fixes for snapshots returning 400 on XML 1.1 and handles some configuration errors more gracefully.
👷♂️ All changes
NmcpAggregationExtension.localRepository()GradleUp#234v1.4.12025-12-30
Nmcp 1.4.1 refines the aggregation dependency resolution to avoid including by mistake projects that do not apply
com.gradleup.nmcp.👷 All changes
Configuration
📅 Schedule: (UTC)
🚦 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.