Bump codacy/codacy-analysis-cli-action from 1.1.0 to 4.3.0

[dependabot[bot]]

Bumps codacy/codacy-analysis-cli-action from 1.1.0 to 4.3.0.

Release notes

Sourced from codacy/codacy-analysis-cli-action's releases.

Move tools to artifact

No release notes provided.

Add max-tool-memory flag

No release notes provided.

Introduce new versioning scheme

Now the versions will be published in the form of v4, v4.1 and v4.1.0.

Allow running Codacy Standalone tools

This release adds support for running Gosec, Clang-tidy, and many more standalone tools from the action.

Skip Uncommitted Changes

It's now possible to skip uncommitted changes using the flag --skip-uncommitted-files-check

Parallel mode runs now tools in parallel

Parallel mode was not working as intended. Now it spawns multiple Docker instances based on the parallelism level

Fix using the correct commit SHA on pull requests

Actions triggered on pull requests now send the reports for the correct commit SHA

Fix staticcheck flow that could change go.mod files

No release notes provided.

Fix standalone tools

Fixes scenario where gosec does not run leading to failure in the next standalone tools.

Add support for account API tokens

No release notes provided.

Fix SARIF output for tools that returns 0 startLine

No release notes provided.

Bump CLI version used in action

• Bump to CLI version to 5.1.4.
• Now, when exporting issues to SARIF it no longer downgrades issues' severities for security patterns.

Commits

• 5cc54a7 feat: build for release
• d43127f feat: build for release
• 8abcaf1 feat: build for release
• 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 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 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)

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.