Update dependency semgrep to v1.111.0 #257
Open
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.108.0
->==1.111.0
Release Notes
returntocorp/semgrep (semgrep)
v1.111.0
Compare Source
Changed
.semgrepignore
file lookup using theSEMGREP_R2C_INTERNAL_EXPLICIT_SEMGREPIGNORE
environment variable. This was used by semgrep-action whichhas been deprecated. (semgrep-action)
Fixed
in JS/TS. (code-8065)
the project root to reduce inaccuracies in module resolution. This change
mitigates the risk of resolving module specifiers to incorrect paths,
particularly in cases involving common library names (e.g.,
django
). (code-8146)findings when using the --gitlab-secrets flag. (scrt-833)
v1.110.0
Compare Source
Added
pro: Inter-file analysis will now process Javascript and Typescript files
together, so that taint can be tracked across both languages. (code-8076)
Pro: new
metavariable-name
operator which allows for expressing a constraintagainst the fully qualified name or nearest equivalent of a metavariable
(useful mainly in JavaScript and TypeScript, where there is no first-class
syntax for this, or where such names or pseudo-names containt symbols which
cannot appear in identifiers). Requires pro naming passes and works best with
interfile naming.
Additional documentation forthcoming. (code-8121)
Changed
Fixed
Fixed a regression in pro interfile mode where type inference for the
var
keyword in Java was not functioning correctly. (code-7991)
PRO: Fix the
range not found
error when using a metavariable pattern match ona typed metavariable. For example, the following metavariable pattern rule will
no longer trigger the error:
lsp will no longer send diagnostics where the message is
MarkupContent
sinceour current implementation does not discriminate on the client capability for
recieiving such diagnostics (to-be-added in 3.18). (code-8120)
Yarn.lock parser now correctly denotes NPM organization scope. (sc-2107)
Packages in
Package.resolved
without a version are now ignored. (sc-2116)Updated
Package.swift
parser to support:v1.109.0
Compare Source
Changed
Fixed
See https://semgrep.dev/playground/s/ReJQO (code-7967)
to prevent unintended interactions. See https://semgrep.dev/playground/s/7KE0k. (code-8054)
optimized the matching of ordered
..., PAT, ...
patterns. (saf-682)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.