Bump commons.pmd-impl.version from 7.5.0 to 7.6.0

[dependabot]

Bumps commons.pmd-impl.version from 7.5.0 to 7.6.0.
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-javascript from 7.5.0 to 7.6.0

Release notes

Sourced from net.sourceforge.pmd:pmd-javascript'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-jsp from 7.5.0 to 7.6.0

Release notes

Sourced from net.sourceforge.pmd:pmd-jsp'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

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