-
-
Notifications
You must be signed in to change notification settings - Fork 279
upgrade code analyzer to v5 #6386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 19 commits
3a3a468
a324d80
b14795a
15a3ce3
736fec3
4f74eea
297dd0e
172670a
f24a244
d0525ea
041d0d2
7bb138e
7bc1af5
e15bb77
37086de
9394321
7eefddf
f63376a
107bb0b
d04ae85
afddb25
6f1d5b6
e5cb09b
c0c6495
a92768e
9a955f5
7ea6c41
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| !.automation |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -87,6 +87,10 @@ Note: Can be used with `oxsecurity/megalinter@beta` in your GitHub Action mega-l | |
| - [kics](https://www.kics.io) from 2.1.14 to **2.1.15** on 2025-10-26 | ||
| - [cspell](https://github.com/streetsidesoftware/cspell/tree/master/packages/cspell) from 9.2.1 to **9.2.2** on 2025-10-26 | ||
| - [terragrunt](https://terragrunt.gruntwork.io) from 0.91.1 to **0.91.5** on 2025-10-26 | ||
| - [powershell_formatter](https://github.com/PowerShell/PSScriptAnalyzer) from 7.5.4 to **5.1.26100** on 2025-10-27 | ||
| - [powershell](https://github.com/PowerShell/PSScriptAnalyzer) from 7.5.4 to **5.1.26100** on 2025-10-27 | ||
| - [git_diff](https://git-scm.com) from 2.49.1 to **2.47.0** on 2025-10-27 | ||
| - [bash-exec](https://www.gnu.org/software/bash/) from 5.2.37 to **5.1.4** on 2025-10-27 | ||
|
||
| <!-- linter-versions-end --> | ||
|
|
||
| ## [v9.1.0] - 2025-10-07 | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| # ====================================================================== | ||
| # CODE ANALYZER CONFIGURATION | ||
| # To learn more about this configuration, visit: | ||
| # https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/config-custom.html | ||
| # ====================================================================== | ||
| # Level at which to log messages to log files. | ||
| # Possible values are: | ||
| # 1 or 'Error' - Includes only error messages in the log. | ||
| # 2 or 'Warn' - Includes warning and error messages in the log. | ||
| # 3 or 'Info' - Includes informative, warning, and error messages in the log. | ||
| # 4 or 'Debug' - Includes debug, informative, warning, and error messages in the log. | ||
| # 5 or 'Fine' - Includes fine detail, debug, informative, warning, and error messages in the log. | ||
| # If unspecified, or if specified as null, then the 'Debug' log level will be used. | ||
| log_level: 4 | ||
|
|
||
| # Engine specific custom configuration settings of the format engines.{engine_name}.{property_name} = {value} where: | ||
| # {engine_name} is the name of the engine containing the setting that you want to override. | ||
| # {property_name} is the name of a property that you would like to override. | ||
| # Each engine may have its own set of properties available to help customize that particular engine's behavior. | ||
| engines: | ||
| # ====================================================================== | ||
| # PMD ENGINE CONFIGURATION | ||
| # To learn more about this configuration, visit: | ||
| # https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-pmd.html#pmd-configuration-reference | ||
| # ====================================================================== | ||
| pmd: | ||
|
|
||
| # Whether to turn off the 'pmd' engine so that it is not included when running Code Analyzer commands. | ||
| disable_engine: false | ||
|
|
||
| # Specifies the list of file extensions to associate to each rule language. | ||
| # The rule(s) associated with a given language will run against all the files in your workspace containing one of | ||
| # the specified file extensions. Each file extension can only be associated to one language. If a specific language | ||
| # is not specified, then a set of default file extensions for that language will be used. | ||
| file_extensions: | ||
| apex: | ||
| - .cls | ||
| - .trigger | ||
| html: | ||
| - .html | ||
| - .htm | ||
| - .xhtml | ||
| - .xht | ||
| - .shtml | ||
| - .cmp | ||
| javascript: | ||
| - .js | ||
| - .cjs | ||
| - .mjs | ||
| typescript: | ||
| - .ts | ||
| visualforce: | ||
| - .page | ||
| - .component | ||
| xml: | ||
| - .xml | ||
|
|
||
| # List of xml ruleset files containing custom PMD rules to be made available for rule selection. | ||
| # Each ruleset must be an xml file that is either: | ||
| # - on disk (provided as an absolute path or a relative path to 'config_root') | ||
| # - or a relative resource found on the Java classpath. | ||
| # Not all custom rules can be fully defined within an xml ruleset file. For example, Java based rules may be defined in jar files. | ||
| # In these cases, you will need to also add your additional files to the Java classpath using the 'java_classpath_entries' field. | ||
| # See https://pmd.github.io/pmd/pmd_userdocs_making_rulesets.html to learn more about PMD rulesets. | ||
| custom_rulesets: [ | ||
| ./apex-pmd-ruleset.xml | ||
| ] | ||
|
|
||
| # ====================================================================== | ||
| # END OF CODE ANALYZER CONFIGURATION | ||
| # ====================================================================== |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -401,7 +401,7 @@ RUN sf plugins install @salesforce/plugin-packaging@${NPM_SALESFORCE_PLUGIN_PACK | |
| ENV SF_AUTOUPDATE_DISABLE=true SF_CLI_DISABLE_AUTOUPDATE=true | ||
| # Linter install | ||
| # renovate: datasource=npm depName=@salesforce/sfdx-scanner | ||
| ARG SALESFORCE_SFDX_SCANNER_VERSION=4.12.0 | ||
| ARG SALESFORCE_SFDX_SCANNER_VERSION=5.5.0 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Renovate Config Mismatch in DocumentationDocumentation shows incorrect installation instructions. The renovate comment on line 403 still references There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Version mismatch: scanner version misdocumentedThe Additional Locations (2) |
||
| RUN sf plugins install @salesforce/sfdx-scanner@${SALESFORCE_SFDX_SCANNER_VERSION} \ | ||
| && (npm cache clean --force || true) \ | ||
| && rm -rf /root/.npm/_cacache | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -398,7 +398,7 @@ RUN sf plugins install @salesforce/plugin-packaging@${NPM_SALESFORCE_PLUGIN_PACK | |
| ENV SF_AUTOUPDATE_DISABLE=true SF_CLI_DISABLE_AUTOUPDATE=true | ||
| # Linter install | ||
| # renovate: datasource=npm depName=@salesforce/sfdx-scanner | ||
| ARG SALESFORCE_SFDX_SCANNER_VERSION=4.12.0 | ||
| ARG SALESFORCE_SFDX_SCANNER_VERSION=5.5.0 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Incorrect Package Reference in DocumentationDocumentation shows incorrect installation instructions. The renovate comment on line 400 still references There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Incorrect scanner version regression in plugin updaterThe |
||
| RUN sf plugins install @salesforce/sfdx-scanner@${SALESFORCE_SFDX_SCANNER_VERSION} \ | ||
| && (npm cache clean --force || true) \ | ||
| && rm -rf /root/.npm/_cacache | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -399,7 +399,7 @@ RUN sf plugins install @salesforce/plugin-packaging@${NPM_SALESFORCE_PLUGIN_PACK | |
| ENV SF_AUTOUPDATE_DISABLE=true SF_CLI_DISABLE_AUTOUPDATE=true | ||
| # Linter install | ||
| # renovate: datasource=npm depName=@salesforce/sfdx-scanner | ||
| ARG SALESFORCE_SFDX_SCANNER_VERSION=4.12.0 | ||
| ARG SALESFORCE_SFDX_SCANNER_VERSION=5.5.0 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Outdated Package Reference in DocumentationDocumentation shows incorrect installation instructions. The renovate comment on line 401 still references
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm trying to find why it is bumped to 5.5.0, if reverted back to adding a new key for the code-analyzer version of the linters. That version doesn't exist in sfdx scanner. |
||
| RUN sf plugins install @salesforce/sfdx-scanner@${SALESFORCE_SFDX_SCANNER_VERSION} \ | ||
| && (npm cache clean --force || true) \ | ||
| && rm -rf /root/.npm/_cacache | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.