Bump semgrep from 0.91.0 to 1.91.0 in /dependencies/python

[dependabot]

Bumps semgrep from 0.91.0 to 1.91.0.

Release notes

Sourced from semgrep's releases.

Release v1.91.0

1.91.0 - 2024-10-10

Added

• Type inference in the Pro engine has been improved for class fields in TypeScript that are assigned a new instance but lack an explicit type definition. When no explicit type is provided for a class field, its type is inferred from the type of the expression assigned to it. For example, in the class definition class Foo { private readonly bar = new Bar(); }, the type of bar is inferred to be Bar. (code-7635)
• Cargo.lock parser can now associate dependencies with lockfile line numbers (sc-1140)

Fixed

• Address python rich.errors.LiveError where attempting to display multiple progress bars raises an exception as flagged in #10562. (grow-414)
• C: Fix a regression causing pattern -n to sometimes not match code -n. (saf-1592)
• When a scan runs into an exception, the app is appropriately notified about the failure. Previously, in the app, it would seem to the user that the scan is still in progress. (sms-502)

Release v1.90.0

1.90.0 - 2024-09-25

Added

• Expanded support for requirement lockfiles. Semgrep will now find any *requirement*.txt file and lockfiles in a requirements folder (**/requirements/*.txt). This functionality will be gated behind the --enable-experimental-requirements CLI flag. (sc-1752)

Changed

• Security update for code snippet storage & access methods. (gh-2038)

Fixed

• Errors that occur in semgrep scans with jobs > 1 will now have more detail (SAF-1628)
• Dockerfile matching: CMD $...ARGS now behaves like CMD ... and matches any CMD instruction that uses the array syntax such as CMD ["ls"]. This

... (truncated)

Changelog

Sourced from semgrep's changelog.

1.91.0 - 2024-10-10

Added

• Type inference in the Pro engine has been improved for class fields in TypeScript that are assigned a new instance but lack an explicit type definition. When no explicit type is provided for a class field, its type is inferred from the type of the expression assigned to it. For example, in the class definition class Foo { private readonly bar = new Bar(); }, the type of bar is inferred to be Bar. (code-7635)
• Cargo.lock parser can now associate dependencies with lockfile line numbers (sc-1140)

Fixed

• Address python rich.errors.LiveError where attempting to display multiple progress bars raises an exception as flagged in #10562. (grow-414)
• C: Fix a regression causing pattern -n to sometimes not match code -n. (saf-1592)
• When a scan runs into an exception, the app is appropriately notified about the failure. Previously, in the app, it would seem to the user that the scan is still in progress. (sms-502)

1.90.0 - 2024-09-25

Added

• Expanded support for requirement lockfiles. Semgrep will now find any *requirement*.txt file and lockfiles in a requirements folder (**/requirements/*.txt). This functionality will be gated behind the --enable-experimental-requirements CLI flag. (sc-1752)

Changed

• Security update for code snippet storage & access methods. (gh-2038)

Fixed

• Errors that occur in semgrep scans with jobs > 1 will now have more detail (SAF-1628)
• Dockerfile matching: CMD $...ARGS now behaves like CMD ... and matches any CMD instruction that uses the array syntax such as CMD ["ls"]. This fix also applies to the other command-like instructions RUN

... (truncated)

Commits

• 1de480b chore: release version 1.91.0
• 2497db0 Apparently it is
• 5a6d582 Try removing the opam update to validate if this was a caching issue
• 51ebb24 Try running opam update
• 8b0a9d8semgrep/semgrep-proprietary#2399
• c0b1947semgrep/semgrep-proprietary#2395
• c76c721semgrep/semgrep-proprietary#2394
• 5c0b82csemgrep/semgrep-proprietary#2395
• 3d47b3a pysemgrep test: skip the prook: and proruleid: annotations (semgrep/semgrep-p...
• 7414fa9 fix: cli does not notify app when scan has an exception (semgrep/semgrep-prop...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1903.