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

chore(deps): update pre-commit hook returntocorp/semgrep to v1.95.0 #597

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

alma-renovate-bot[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
returntocorp/semgrep repository minor v1.93.0 -> v1.95.0

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.


Release Notes

returntocorp/semgrep (returntocorp/semgrep)

v1.95.0

Compare Source

1.95.0 - 2024-10-31

Changed
  • Remove deprecated --enable-experimental-requirements flag. Functionality has
    been always enabled since Semgrep 1.93.0. (ssc-1903)
Fixed
  • osemgrep: Running osemgrep with the Pro Engine now correctly runs rules with proprietary languages (saf-1686)
  • Fixed bug where semgrep would crash if --trace was passed (saf-tracing)

v1.94.0

Compare Source

1.94.0 - 2024-10-30

Fixed
  • pro: taint-mode: Semgrep should no longer confuse a return in a lambda with
    a return in its enclosing function.

    E.g. In the example below the return value of foo is NOT tainted:

    function foo() {
        bar(() => taint);
        return ok;
    } (code-7657)
    
  • OCaml: matching will now recognized "local open" so that a pattern like
    Foo.bar ... will now correctly match code such as let open Foo in bar 1
    or Foo.(bar 1) in addition to the classic Foo.bar 1. (local_open)

  • Project files lacking sufficient read permissions are now skipped gracefully
    by semgrep. (saf-1598)

  • Semgrep will now print stderr and additional debugging info when semgrep-core
    exits with a fatal error code but still returns a json repsonse (finishes
    scanning) (saf-1672)

  • semgrep ci should parse correctly git logs to compute the set of contributors
    even if some authors have special characters in their names. (saf-1681)


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@alma-renovate-bot alma-renovate-bot bot requested a review from a team as a code owner November 4, 2024 10:14
@alma-renovate-bot alma-renovate-bot bot requested a review from a team November 4, 2024 10:14
Copy link

sonarcloud bot commented Nov 4, 2024

Copy link

github-actions bot commented Nov 4, 2024

⏳E2E tests are currently running.
➡️ You can follow their progression here.

Copy link

github-actions bot commented Nov 4, 2024

❌ E2E tests have failed.
➡️ You can find the results here.

@Benjamin-Freoua-Alma Benjamin-Freoua-Alma merged commit 609ba97 into develop Nov 7, 2024
5 of 6 checks passed
@Benjamin-Freoua-Alma Benjamin-Freoua-Alma deleted the renovate/pre-commit-repositories branch November 7, 2024 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants