build(deps): bump nmcp from 1.5.0 to 1.6.0

[dependabot]

Bumps nmcp from 1.5.0 to 1.6.0.
Updates com.gradleup.nmcp from 1.5.0 to 1.6.0

Release notes

Sourced from com.gradleup.nmcp's releases.

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!

Changelog

Sourced from com.gradleup.nmcp's changelog.

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)
}

Commits

• 431b572 Switch to USER_MANAGED
• b6ffb40 Remove another place where checksums where added (#259)
• 942bcd8 Do not publish checksums for maven-metadata (#258)
• 4ad0a51 Update dependencies (#257)
• cf04ce0 Filter out checksums (#256)
• 7ef98bf Version is now 1.5.1-SNAPSHOT (#254)
• See full diff in compare view

Updates com.gradleup.nmcp.aggregation from 1.5.0 to 1.6.0

Release notes

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

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!

Changelog

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

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)
}

Commits

• 431b572 Switch to USER_MANAGED
• b6ffb40 Remove another place where checksums where added (#259)
• 942bcd8 Do not publish checksums for maven-metadata (#258)
• 4ad0a51 Update dependencies (#257)
• cf04ce0 Filter out checksums (#256)
• 7ef98bf Version is now 1.5.1-SNAPSHOT (#254)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)