codingstyle
codingstyle copied to clipboard
Bump pmd.version from 7.5.0 to 7.6.0
Bumps pmd.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
- 🐛 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
mainfrom 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 --autoMore 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
mainas
... (truncated)
Commits
d8d4d3d[release] prepare release pmd_releases/7.6.06d48907Prepare pmd release 7.6.05261a6d[doc] Update contributorsac8c873[apex] Support convertCurrency() in SOQL/SOSL (#5237)c2445c7[doc] Documentation update for --show-suppressed flag (#5230)03fba24[doc] Update@dschachas a contributor6f518c8[doc] Improve doc for --show-suppressedc84ffb8[apex] Bump apex-parser from 4.2.0 to 4.3.074f9d75[apex] Support convertCurrency() in SOQL/SOSLa2b5ae6Bump 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
- 🐛 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
mainfrom 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 --autoMore 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
mainas
... (truncated)
Commits
d8d4d3d[release] prepare release pmd_releases/7.6.06d48907Prepare pmd release 7.6.05261a6d[doc] Update contributorsac8c873[apex] Support convertCurrency() in SOQL/SOSL (#5237)c2445c7[doc] Documentation update for --show-suppressed flag (#5230)03fba24[doc] Update@dschachas a contributor6f518c8[doc] Improve doc for --show-suppressedc84ffb8[apex] Bump apex-parser from 4.2.0 to 4.3.074f9d75[apex] Support convertCurrency() in SOQL/SOSLa2b5ae6Bump 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
- 🐛 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
mainfrom 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 --autoMore 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
mainas
... (truncated)
Commits
d8d4d3d[release] prepare release pmd_releases/7.6.06d48907Prepare pmd release 7.6.05261a6d[doc] Update contributorsac8c873[apex] Support convertCurrency() in SOQL/SOSL (#5237)c2445c7[doc] Documentation update for --show-suppressed flag (#5230)03fba24[doc] Update@dschachas a contributor6f518c8[doc] Improve doc for --show-suppressedc84ffb8[apex] Bump apex-parser from 4.2.0 to 4.3.074f9d75[apex] Support convertCurrency() in SOQL/SOSLa2b5ae6Bump 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
:sunny: Quality Monitor
:vertical_traffic_light: Tests: 98 % successful (:heavy_check_mark: 95 passed, :see_no_evil: 2 skipped)
:wavy_dash: Line Coverage: 91% (63 missed lines)
:curly_loop: Branch Coverage: 91% (19 missed branches)
Mutation Coverage: 80% (78 survived mutations)
CheckStyle: No warnings
PMD: No warnings
SpotBugs: No warnings
:bug: Error Prone: No warnings
OWASP Dependency Check: No warnings
Created by Quality Monitor v1.10.0 (#9c48d50). More details are shown in the GitHub Checks Result.