Skip to content

build(deps): bump com.gradleup.nmcp:nmcp from 1.2.1 to 1.6.1 - #517

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/com.gradleup.nmcp-nmcp-1.6.0
Closed

build(deps): bump com.gradleup.nmcp:nmcp from 1.2.1 to 1.6.1#517
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/com.gradleup.nmcp-nmcp-1.6.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 22, 2026

Copy link
Copy Markdown
Contributor

Bumps com.gradleup.nmcp:nmcp from 1.2.1 to 1.6.1.

Release notes

Sourced from com.gradleup.nmcp:nmcp's releases.

v1.6.1

v 1.6.1 restores some checksums:

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 💙

On a separate note, this version also deprecates publishAllPublicationsToMavenCentral in favor of using either the aggregation or the settings plugin.

v1.6.0

Nmcp 1.6.0 stops publishing the following checksums:

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

This is all disabled by default.

If you like the checksums, you can send them again by setting publishAllChecksums:

nmcpAggregation {
  publishAllChecksums.set(true)
}

If you do, please let me know why, I'm curious!

1.5.0

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

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

... (truncated)

Changelog

Sourced from com.gradleup.nmcp:nmcp's changelog.

Version 1.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 💙

Version 1.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)
}

Version 1.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!

Version 1.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.

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jun 22, 2026
@dependabot
dependabot Bot requested review from a team as code owners June 22, 2026 22:23
@dependabot
dependabot Bot requested a review from jjohannes June 22, 2026 22:23
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 22, 2026
@dependabot
dependabot Bot requested a review from san-est June 22, 2026 22:23
@dependabot dependabot Bot added the java Pull requests that update Java code label Jun 22, 2026
@dependabot
dependabot Bot force-pushed the dependabot/gradle/com.gradleup.nmcp-nmcp-1.6.0 branch from f066d00 to 69a44cc Compare June 25, 2026 13:14
Bumps [com.gradleup.nmcp:nmcp](https://github.com/gradleup/nmcp) from 1.2.1 to 1.6.1.
- [Release notes](https://github.com/gradleup/nmcp/releases)
- [Changelog](https://github.com/GradleUp/nmcp/blob/main/CHANGELOG.md)
- [Commits](GradleUp/nmcp@v1.2.1...v1.6.1)

---
updated-dependencies:
- dependency-name: com.gradleup.nmcp:nmcp
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps): bump com.gradleup.nmcp:nmcp from 1.2.1 to 1.6.0 build(deps): bump com.gradleup.nmcp:nmcp from 1.2.1 to 1.6.1 Jul 2, 2026
@dependabot
dependabot Bot force-pushed the dependabot/gradle/com.gradleup.nmcp-nmcp-1.6.0 branch from 69a44cc to f9eda61 Compare July 2, 2026 06:14
@dependabot @github

dependabot Bot commented on behalf of github Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #531.

@dependabot dependabot Bot closed this Jul 2, 2026
@dependabot
dependabot Bot deleted the dependabot/gradle/com.gradleup.nmcp-nmcp-1.6.0 branch July 2, 2026 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant