chore(deps): update dependency semgrep to ~=1.103.0 #732
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~=1.101.0
->~=1.103.0
Release Notes
returntocorp/semgrep (semgrep)
v1.103.0
Compare Source
Added
pro: taint: Support for lambdas as callbacks.
pro: python: Semgrep will now consider top-level lambdas like
x
below forinter-procedural analysis:
Changed
pip
from the Semgrep Docker image. If you need it, you may install it by runningapk add py3-pip
. (saf-1774)Fixed
with
s, like this:with (
f() as a,
g() as b,
):
pass
``` (saf-1802)
v1.102.0
Compare Source
Added
Fixed
semgrep test
andsemgrep validate
commands have beencorrectly documented as EXPERIMENTAL (in semgrep --help).
Those commands are not GA yet and people should still
use the
semgrep scan --test
andsemgrep scan --validate
(orthe variants without the implicit "scan") commands (unless
they want to experiment with getting results faster and are ok
with incomplete coverage of the legacy
semgrep --test
and
semgrep --validate
). (experimental)If such a path is passed explicitly as a scanning root on the
command line, it results in an error. Otherwise if it's a file discovered
while scanning the file system, it's a warning. (saf-1776)
should now be more robust and not abort the whole scan when
an out of bound line access happens during the nosemgrep analysis
or when outputing the lines of a match. (saf-1778)
Configuration
📅 Schedule: Branch creation - "* 0-4 * * 3" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.