Skip to content

chore(deps): update returntocorp/semgrep docker tag to v1.118.0 #1836

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

Merged
merged 1 commit into from
Apr 9, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 9, 2025

This PR contains the following updates:

Package Type Update Change
returntocorp/semgrep container minor 1.117.0 -> 1.118.0

Release Notes

semgrep/semgrep (returntocorp/semgrep)

v1.118.0

Compare Source

Fixed
  • Pro: Failure to parse a package.json file when analysing JavaScript or
    TypeScript is no longer a fatal error. (code-8227)

  • taint-mode: Fixed bug in taint "auto-cleaning" where we automatically clean the
    LHS of an assigmnet if the RHS is clean, provided that the LHS is not subject to
    any "side-effects". In some cases, this could cause the taint analysis to timeout.
    Some combinations of rules and repos will see a major perf improvement, in other
    cases it may not be noticeable. (code-8288)

  • In a Semgrep rule's metadata section, two fields may provide URLs:

    • source: populated dynamically by the Semgrep registry serving the rule, it's a URL that
      offers information about the rule.
    • source-rule-url: optional string, a URL for the source of inspiration for the rule.

    The SARIF format supports only one URL under the field helpUri.
    Previously, Semgrep populated the SARIF helpUri field only with metadata.source.
    This fix is to use metadata.source if available, otherwise falling back to metadata.source-rule-url.

    Contributed by @​candrews. (gh-10891)


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.

🔕 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.

@renovate renovate bot enabled auto-merge April 9, 2025 06:44
Copy link
Contributor

github-actions bot commented Apr 9, 2025

Test results

6 tests  ±0   6 ✅ ±0   0s ⏱️ ±0s
2 suites ±0   0 💤 ±0 
1 files   ±0   0 ❌ ±0 

Results for commit b3f6b3d. ± Comparison against base commit 0ddfe82.

♻️ This comment has been updated with latest results.

Copy link

codecov bot commented Apr 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.48%. Comparing base (0ddfe82) to head (b3f6b3d).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1836   +/-   ##
=======================================
  Coverage   79.48%   79.48%           
=======================================
  Files           2        2           
  Lines          39       39           
=======================================
  Hits           31       31           
  Misses          8        8           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/returntocorp-semgrep-1.x branch from 565ffb5 to b3f6b3d Compare April 9, 2025 11:03
@renovate renovate bot merged commit fde2f12 into main Apr 9, 2025
17 checks passed
@renovate renovate bot deleted the renovate/returntocorp-semgrep-1.x branch April 9, 2025 11:05
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