Bump com.gradleup.nmcp.settings from 1.6.0 to 1.6.1 in the dev-dependencies group

[dependabot]

Bumps the dev-dependencies group with 1 update: com.gradleup.nmcp.settings.

Updates com.gradleup.nmcp.settings from 1.6.0 to 1.6.1

Release notes

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

v1.6.1

v 1.6.1 restores some checksums:

• maven-metadata.md5 and 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 💙

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

Changelog

Sourced from com.gradleup.nmcp.settings'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 💙

Commits

• f0114cb Also publish checksums for the artifact metadata
• 6e57dbc Update bootstrap nmcp
• bc10949 Reintroduce some checksums (#266)
• 1f34b28 Deprecate publishAllPublicationsToCentralPortal (#264)
• 92e0f77 Version is now 1.6.1-SNAPSHOT (#261)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions