Skip to content
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

⬆️ Updates codacy/codacy-analysis-cli-action action to v4 #366

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2021

This PR contains the following updates:

Package Type Update Change
codacy/codacy-analysis-cli-action action major 1.1.0 -> v4.4.5

Release Notes

codacy/codacy-analysis-cli-action (codacy/codacy-analysis-cli-action)

v4.4.5

Compare Source

What's Changed

v4.4.4

Compare Source

What's Changed

v4.4.3

Compare Source

What's Changed

v4.4.2

Compare Source

What's Changed

New Contributors

Full Changelog: codacy/codacy-analysis-cli-action@4.0.2...v4.4.2

v4.4.1

Compare Source

v4.4.0: Update cli and tool versions

Compare Source

Update versions of:

  • staticheck
  • gosec
  • codacy-analysis-cli

v4.3.0: Move tools to artifact

Compare Source

v4.2.0: Add max-tool-memory flag

Compare Source

v4.1.0: Introduce new versioning scheme

Compare Source

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

v4.0.2: Allow running Codacy Standalone tools

Compare Source

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

v4.0.1: Skip Uncommitted Changes

Compare Source

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

v4.0.0: Parallel mode runs now tools in parallel

Compare Source

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

v3.0.3: Fix using the correct commit SHA on pull requests

Compare Source

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

v3.0.2: Fix staticcheck flow that could change go.mod files

Compare Source

v3.0.1: Fix standalone tools

Compare Source

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

v3.0.0: Add support for account API tokens

Compare Source

v2.0.1: Fix SARIF output for tools that returns 0 startLine

Compare Source

v2.0.0: Bump CLI version used in action

Compare Source

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

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changelogg
Copy link

changelogg bot commented Oct 18, 2021

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

@github-actions
Copy link

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

@github-actions
Copy link

🏷️ [bumpr] Next version:v2.0.2 Changes:v2.0.1...AlexRogalskiy:renovate/codacy-codacy-analysis-cli-action-4.x

@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 264e64d to 543857c Compare March 7, 2022 14:04
@viezly
Copy link

viezly bot commented Mar 7, 2022

Pull request by bot. No need to analyze

@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 543857c to 1df4ce3 Compare March 26, 2022 14:37
@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 1df4ce3 to 50d436a Compare June 18, 2022 18:49
@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 50d436a to 053d265 Compare September 25, 2022 11:29
@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 053d265 to f09ba43 Compare March 17, 2023 08:14
@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from f09ba43 to 6eb3826 Compare February 8, 2024 16:28
@github-advanced-security
Copy link

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.

@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 6eb3826 to bbc7e1a Compare May 8, 2024 09:23
@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from bbc7e1a to 75ad18e Compare July 11, 2024 15:00
@@ -25,7 +25,7 @@

# Execute Codacy Analysis CLI and generate a SARIF output with the security issues identified during the analysis
- name: Run Codacy Analysis CLI
uses: codacy/codacy-analysis-cli-action@1.1.0
uses: codacy/codacy-analysis-cli-action@v4.4.4

Check warning

Code scanning / Semgrep (reported by Codacy)

An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Warning

An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release.
@renovate renovate bot force-pushed the renovate/codacy-codacy-analysis-cli-action-4.x branch from 75ad18e to 5dc9c2a Compare July 12, 2024 16:32
@@ -25,7 +25,7 @@

# Execute Codacy Analysis CLI and generate a SARIF output with the security issues identified during the analysis
- name: Run Codacy Analysis CLI
uses: codacy/codacy-analysis-cli-action@1.1.0
uses: codacy/codacy-analysis-cli-action@v4.4.5

Check warning

Code scanning / Semgrep (reported by Codacy)

An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Warning

An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants