chore(deps): Bump the all-maven-dependencies group across 2 directories with 8 updates

[dependabot]

Bumps the all-maven-dependencies group with 7 updates in the / directory:

Package	From	To
org.junit:junit-bom	5.11.0	5.11.1
org.jetbrains:annotations	24.1.0	25.0.0
com.puppycrawl.tools:checkstyle	10.18.1	10.18.2
net.sourceforge.pmd:pmd-core	7.5.0	7.6.0
net.sourceforge.pmd:pmd-java	7.5.0	7.6.0
org.apache.maven.plugins:maven-gpg-plugin	3.2.6	3.2.7
org.cyclonedx:cyclonedx-maven-plugin	2.8.1	2.8.2

Bumps the all-maven-dependencies group with 1 update in the /scram-client/src/it/jpms-scram-client directory: org.junit.jupiter:junit-jupiter.

Updates org.junit:junit-bom from 5.11.0 to 5.11.1

Release notes

Sourced from org.junit:junit-bom's releases.

JUnit 5.11.1 = Platform 1.11.1 + Jupiter 5.11.1 + Vintage 5.11.1

See Release Notes.

Full Changelog: junit-team/junit5@r5.11.0...r5.11.1

Commits

• e4b2c0c Release 5.11.1
• c37b179 Finalize 5.11.1 release notes
• a7b1c49 Include 5.10.4 release notes
• 3646b7d Document benefits of messageSupplier in Assertions (#3938)
• 6b9f15d Delete unnecessary (and potentially misleading) comment in User Guide
• 98dafd3 Reduce flakiness
• 6529d8d Allow for work stealing when only holding read locks (#4012)
• 0d25a5a Fix YAML syntax
• 28dd375 Fix step label
• 348ef61 Switch to Temurin for JDK 23 (#4005)
• Additional commits viewable in compare view

Updates org.jetbrains:annotations from 24.1.0 to 25.0.0

Release notes

Sourced from org.jetbrains:annotations's releases.

25.0.0

• Added Kotlin Multiplatform artifact (multiplatform-annotations).
• Removed Java 5 artifact.

Changelog

Sourced from org.jetbrains:annotations's changelog.

Version 25.0.0

• Added Kotlin Multiplatform artifact (multiplatform-annotations).
• Removed Java 5 artifact.

Commits

• daa4789 Merge pull request #112 from serjsysoev/signall
• b1d593d Add signAll task that signs all artifacts
• e1ad90f Merge pull request #111 from serjsysoev/multiplatform-publication
• 229e51a Add javadoc and common sources publishing
• 5d7e023 Set up multiplatform publishing maintaining jvm artifact name
• bc94c2f Move the multiplatform project to the root
• 7bc931a Make multiplatform expect/actual implicitly actualizing declarations with jav...
• 42bb869 Fix multiplatform artifact module-info.java
• 243b2f7 Remove Java artifact
• a1060cd Move java annotations to jvm part of multiplatform artifact
• Additional commits viewable in compare view

Updates com.puppycrawl.tools:checkstyle from 10.18.1 to 10.18.2

Release notes

Sourced from com.puppycrawl.tools:checkstyle's releases.

checkstyle-10.18.2

Checkstyle 10.18.2 - https://checkstyle.org/releasenotes.html#Release_10.18.2

Bug fixes:

#15690 - JavadocParagraph: allowNewlineParagraph should allow '\n' after P tag and content start from new line #15642 - google_checks: Section 4.1.3 should not be covered by EmptyBlock and EmptyCatchBlock #15609 - google_checks SuppressionXpathSingleFilter for 'MethodName' check is too lenient in several ways #15434 - MissingJavadocMethod does not give warning for missing javadoc for protected methods in google_checks.xml #13553 - False positive in FallThroughCheck on last case #15233 - Suppression for long identifiers for 4.4 Column Limit: 100 rule of google java style guide #15414 - Google style: Javadoc is optional for "simple, obvious" members

Commits

• 3651c45 [maven-release-plugin] prepare release checkstyle-10.18.2
• ca569e6 doc: release notes for 10.18.2
• 4eec526 Issue #6207: add class data abstraction coupling xpath regression tests
• fe4fde1 infra: fix link in exclude for jdepend-maven-plugin to fix run of maven-linkc...
• 50cdde7 Issue #15456: Specify violation message for Nested Block (#11)
• b1d923e Issue #15690: fix allowNewlineParagraph at JavadocParagraphCheck
• b41666f dependency: bump org.apache.maven.plugins:maven-gpg-plugin
• 4c378dc supplemental: added violation messages in JavadocParagraph's input files
• 82bc795 dependency: bump junit.version from 5.11.0 to 5.11.1
• 4704b0f Issue #6207: Add XPath IT Regression Test for ModifiedControlVariable
• Additional commits viewable in compare view

Updates net.sourceforge.pmd:pmd-core from 7.5.0 to 7.6.0

Release notes

Sourced from net.sourceforge.pmd:pmd-core's releases.

PMD 7.6.0 (27-September-2024)

27-September-2024 - 7.6.0

The PMD team is pleased to announce PMD 7.6.0.

This is a minor release.

Table Of Contents

• 🚀 New and noteworthy
  • New Git default branch - "main"
• 🐛 Fixed Issues
• 🚨 API Changes
• ✨ Merged pull requests
• 📦 Dependency updates
• 📈 Stats

🚀 New and noteworthy

New Git default branch - "main"

We are joining the Git community and updating "master" to "main". Using the term "master" for the main development branch can be offensive to some people. Existing versions of Git have been always capable of working with any branch name and since 2.28.0 (July 2020) the default initial branch is configurable (init.defaultBranch). Since October 2020, the default branch for new repositories on GitHub is "main". Finally, PMD will also use this new name for the main branch in all our own repositories.

Why "main"? PMD uses a very simple branching model - pull requests with feature branches and one main development branch, from which releases are created. That's why "main" is currently the best fitting name.

More information:

• https://sfconservancy.org/news/2020/jun/23/gitbranchname/
• https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main/

What changes?

• We change the default branch on GitHub, so that pull requests are automatically created against main from now on.

• If you have already a local clone of PMD's repository, you'll need to rename the old master branch locally:

  git branch --move master main
  git fetch origin
  git branch --set-upstream-to=origin/main main
  git remote set-head origin --auto
  

  More info: https://git-scm.com/book/en/v2/Git-Branching-Branch-Management#_changing_master and https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes

• If you created a fork on GitHub, you'll need to change the default branch in your fork to main as

... (truncated)

Commits

• d8d4d3d [release] prepare release pmd_releases/7.6.0
• 6d48907 Prepare pmd release 7.6.0
• 5261a6d [doc] Update contributors
• ac8c873 [apex] Support convertCurrency() in SOQL/SOSL (#5237)
• c2445c7 [doc] Documentation update for --show-suppressed flag (#5230)
• 03fba24 [doc] Update @​dschach as a contributor
• 6f518c8 [doc] Improve doc for --show-suppressed
• c84ffb8 [apex] Bump apex-parser from 4.2.0 to 4.3.0
• 74f9d75 [apex] Support convertCurrency() in SOQL/SOSL
• a2b5ae6 Bump build-tools from 27-SNAPSHOT to 27
• Additional commits viewable in compare view

Updates net.sourceforge.pmd:pmd-java from 7.5.0 to 7.6.0

Release notes

Sourced from net.sourceforge.pmd:pmd-java's releases.

PMD 7.6.0 (27-September-2024)

27-September-2024 - 7.6.0

The PMD team is pleased to announce PMD 7.6.0.

This is a minor release.

Table Of Contents

• 🚀 New and noteworthy
  • New Git default branch - "main"
• 🐛 Fixed Issues
• 🚨 API Changes
• ✨ Merged pull requests
• 📦 Dependency updates
• 📈 Stats

🚀 New and noteworthy

New Git default branch - "main"

We are joining the Git community and updating "master" to "main". Using the term "master" for the main development branch can be offensive to some people. Existing versions of Git have been always capable of working with any branch name and since 2.28.0 (July 2020) the default initial branch is configurable (init.defaultBranch). Since October 2020, the default branch for new repositories on GitHub is "main". Finally, PMD will also use this new name for the main branch in all our own repositories.

Why "main"? PMD uses a very simple branching model - pull requests with feature branches and one main development branch, from which releases are created. That's why "main" is currently the best fitting name.

More information:

• https://sfconservancy.org/news/2020/jun/23/gitbranchname/
• https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main/

What changes?

• We change the default branch on GitHub, so that pull requests are automatically created against main from now on.

• If you have already a local clone of PMD's repository, you'll need to rename the old master branch locally:

  git branch --move master main
  git fetch origin
  git branch --set-upstream-to=origin/main main
  git remote set-head origin --auto
  

  More info: https://git-scm.com/book/en/v2/Git-Branching-Branch-Management#_changing_master and https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes

• If you created a fork on GitHub, you'll need to change the default branch in your fork to main as

... (truncated)

Commits

• d8d4d3d [release] prepare release pmd_releases/7.6.0
• 6d48907 Prepare pmd release 7.6.0
• 5261a6d [doc] Update contributors
• ac8c873 [apex] Support convertCurrency() in SOQL/SOSL (#5237)
• c2445c7 [doc] Documentation update for --show-suppressed flag (#5230)
• 03fba24 [doc] Update @​dschach as a contributor
• 6f518c8 [doc] Improve doc for --show-suppressed
• c84ffb8 [apex] Bump apex-parser from 4.2.0 to 4.3.0
• 74f9d75 [apex] Support convertCurrency() in SOQL/SOSL
• a2b5ae6 Bump build-tools from 27-SNAPSHOT to 27
• Additional commits viewable in compare view

Updates net.sourceforge.pmd:pmd-java from 7.5.0 to 7.6.0

Release notes

Sourced from net.sourceforge.pmd:pmd-java's releases.

PMD 7.6.0 (27-September-2024)

27-September-2024 - 7.6.0

The PMD team is pleased to announce PMD 7.6.0.

This is a minor release.

Table Of Contents

• 🚀 New and noteworthy
  • New Git default branch - "main"
• 🐛 Fixed Issues
• 🚨 API Changes
• ✨ Merged pull requests
• 📦 Dependency updates
• 📈 Stats

🚀 New and noteworthy

New Git default branch - "main"

We are joining the Git community and updating "master" to "main". Using the term "master" for the main development branch can be offensive to some people. Existing versions of Git have been always capable of working with any branch name and since 2.28.0 (July 2020) the default initial branch is configurable (init.defaultBranch). Since October 2020, the default branch for new repositories on GitHub is "main". Finally, PMD will also use this new name for the main branch in all our own repositories.

Why "main"? PMD uses a very simple branching model - pull requests with feature branches and one main development branch, from which releases are created. That's why "main" is currently the best fitting name.

More information:

• https://sfconservancy.org/news/2020/jun/23/gitbranchname/
• https://github.blog/changelog/2020-10-01-the-default-branch-for-newly-created-repositories-is-now-main/

What changes?

• We change the default branch on GitHub, so that pull requests are automatically created against main from now on.

• If you have already a local clone of PMD's repository, you'll need to rename the old master branch locally:

  git branch --move master main
  git fetch origin
  git branch --set-upstream-to=origin/main main
  git remote set-head origin --auto
  

  More info: https://git-scm.com/book/en/v2/Git-Branching-Branch-Management#_changing_master and https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes

• If you created a fork on GitHub, you'll need to change the default branch in your fork to main as

... (truncated)

Commits

• d8d4d3d [release] prepare release pmd_releases/7.6.0
• 6d48907 Prepare pmd release 7.6.0
• 5261a6d [doc] Update contributors
• ac8c873 [apex] Support convertCurrency() in SOQL/SOSL (#5237)
• c2445c7 [doc] Documentation update for --show-suppressed flag (#5230)
• 03fba24 [doc] Update @​dschach as a contributor
• 6f518c8 [doc] Improve doc for --show-suppressed
• c84ffb8 [apex] Bump apex-parser from 4.2.0 to 4.3.0
• 74f9d75 [apex] Support convertCurrency() in SOQL/SOSL
• a2b5ae6 Bump build-tools from 27-SNAPSHOT to 27
• Additional commits viewable in compare view

Updates org.apache.maven.plugins:maven-gpg-plugin from 3.2.6 to 3.2.7

Release notes

Sourced from org.apache.maven.plugins:maven-gpg-plugin's releases.

3.2.7

Fixes a lingering issue affecting whole 3.2.x lineage, that resulted in "bad passphrase" on Windows OS with GPG signer (see MGPG-136 for details).

What's Changed

• [MGPG-136] Windows passphrase corruption by @​cstamas in apache/maven-gpg-plugin#120
• Bump com.kohlschutter.junixsocket:junixsocket-core from 2.10.0 to 2.10.1 by @​dependabot in apache/maven-gpg-plugin#121
• Bump commons-io:commons-io from 2.16.1 to 2.17.0 by @​dependabot in apache/maven-gpg-plugin#119

Full Changelog: apache/maven-gpg-plugin@maven-gpg-plugin-3.2.6...maven-gpg-plugin-3.2.7

Commits

• 43af21c [maven-release-plugin] prepare release maven-gpg-plugin-3.2.7
• 8c5a8d2 [MGPG-144] Bump commons-io:commons-io from 2.16.1 to 2.17.0 (#119)
• cb5422f [MGPG-143] Bump com.kohlschutter.junixsocket:junixsocket-core from 2.10.0 to ...
• 6b2a27f [MGPG-136] Windows passphrase corruption (#120)
• 31e87e0 [maven-release-plugin] prepare for next development iteration
• See full diff in compare view

Updates org.cyclonedx:cyclonedx-maven-plugin from 2.8.1 to 2.8.2

Release notes

Sourced from org.cyclonedx:cyclonedx-maven-plugin's releases.

2.8.2

🐛 Bug Fixes

• display configured classifier from #506 (#550) @​hboutemy

📦 Dependency updates

• Bump plugin-tools.version from 3.13.1 to 3.15.0 (#551) @​dependabot
• Bump org.apache.maven.plugins:maven-project-info-reports-plugin from 3.6.1 to 3.7.0 (#552) @​dependabot
• Bump org.apache.commons:commons-lang3 from 3.14.0 to 3.17.0 (#546) @​dependabot
• Bump commons-codec:commons-codec from 1.17.0 to 1.17.1 (#537) @​dependabot

Commits

• a3f468f [maven-release-plugin] prepare release cyclonedx-maven-plugin-2.8.2
• 85e3bd8 Bump plugin-tools.version from 3.13.1 to 3.15.0
• 314424d Bump org.apache.maven.plugins:maven-project-info-reports-plugin
• 41808a0 display configured classifier from #506
• be1b73a Bump org.apache.commons:commons-lang3 from 3.14.0 to 3.17.0
• bb865c4 Bump commons-codec:commons-codec from 1.17.0 to 1.17.1
• cb74626 [maven-release-plugin] prepare for next development iteration
• See full diff in compare view

Updates org.junit.jupiter:junit-jupiter from 5.11.0 to 5.11.1

Release notes

Sourced from org.junit.jupiter:junit-jupiter's releases.

JUnit 5.11.1 = Platform 1.11.1 + Jupiter 5.11.1 + Vintage 5.11.1

See Release Notes.

Full Changelog: junit-team/junit5@r5.11.0...r5.11.1

Commits

• e4b2c0c Release 5.11.1
• c37b179 Finalize 5.11.1 release notes
• a7b1c49 Include 5.10.4 release notes
• 3646b7d Document benefits of messageSupplier in Assertions (#3938)
• 6b9f15d Delete unnecessary (and potentially misleading) comment in User Guide
• 98dafd3 Reduce flakiness
• 6529d8d Allow for work stealing when only holding read locks (#4012)
• 0d25a5a Fix YAML syntax
• 28dd375 Fix step label
• 348ef61 Switch to Temurin for JDK 23 (#4005)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.