Skip to content

Update plugin com.gradleup.nmcp.aggregation to v1.6.1#1241

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/com.gradleup.nmcp.aggregation
Open

Update plugin com.gradleup.nmcp.aggregation to v1.6.1#1241
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/com.gradleup.nmcp.aggregation

Conversation

@renovate

@renovate renovate Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
com.gradleup.nmcp.aggregation 1.4.01.6.1 age confidence

Release Notes

gradleup/nmcp (com.gradleup.nmcp.aggregation)

v1.6.1

2026-07-01

Restores some checksums:

  • maven-metadata.md5, maven-metadata.sha1 (because maven outputs a scary warning without them)
  • All the .sha512 checksums (because Gradle uses them to validate caches contents)

All in all, nmcp now publishes .md5, .sha1, .sha512 for all files except for signature files (.asc) where no checksums are required.

Long term, I'd love to drop the .md5 and .sha1 checksums. 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.0

2026-06-21

Nmcp 1.6.0 stop publishing the following checksums:

  • signature checksums (.asc.md5, .asc.sha1, .asc.sha256, .asc.sha512)
  • all non-required checksums (.sha256, .sha512)
  • all maven-metadata checksums (for local publishing, maven-metadata.xml is never sent to Central Portal)

You can send the checksums by setting publishAllChecksums

nmcpAggregation {
  publishAllChecksums.set(true)
}

v1.5.0

2026-04-30

Nmcp 1.5.0 adds nmcpPublishDeployment() to publish an existing deployment to the Central Portal (#​251):

./gradlew nmcpPublishDeployment -PnmcpDeploymentId=$deploymentId'

Many thanks @​marcphilipp for the contribution!

v1.4.4

2026-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.3

2026-01-02

Version 1.4.3 adds NmcpAggregationExtension.allowDuplicateProjectNames (#​239) as an escape hatch for the duplicate name check (#​233)

v1.4.2

2025-12-31

Version 1.4.2 fixes for snapshots returning 400 on XML 1.1 and handles some configuration errors more gracefully.

👷‍♂️ All changes

  • Make sure to send XML 1.0 (Fixes 400 error when publishing snapshots) GradleUp#231
  • Add NmcpAggregationExtension.localRepository() GradleUp#234
  • Fail if there are duplicate project names GradleUp#233
  • Display an error if the aggregation is empty GradleUp#236

v1.4.1

2025-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

  • Fix zip files could contain unexpected files GradleUp#227
  • Bump Kotlin, OkHttp, xmlutil and a bunch of other dependencies GradleUp#228

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every 3 weeks on Monday"
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies label Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant