Update semgrep requirement from ~=1.100.0 to ~=1.102.0

[dependabot]

Updates the requirements on semgrep to permit the latest version.

Release notes

Sourced from semgrep's releases.

Release v1.102.0

1.102.0 - 2025-01-08

Added

• Added pro-only support for parsing a dependency graph from package-lock.json v1 files (SC-1858)
• Added pro-only support for parsing a dependency graph from package-lock.json v2 and v3 files (SC-1991)
• The poetry.lock parser can now parse dependency relationships (ssc-1970)
• The Yarn.lock V1 and V2 parsers can parse dependency relationships. (ssc-1988)

Fixed

• The semgrep test and semgrep validate commands have been correctly documented as EXPERIMENTAL (in semgrep --help). Those commands are not GA yet and people should still use the semgrep scan --test and semgrep scan --validate (or the 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)
• Improve error handling for functionality ancillary to a scan (such as looking for nosemgrep comments and rendering autofixes) to reduce the likelihood of an unexpected error in such a component bringing down the entire scan. (saf-1737)
• Fix the behavior of semgrep when running into broken symlinks. 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)
• Fixed another crash due to exception in lines_of_file. The code 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)
• Direct dev dependencies in yarn/npm lockfiles are now correctly marked as direct (sc-1996)

Changelog

Sourced from semgrep's changelog.

1.102.0 - 2025-01-08

Added

• Added pro-only support for parsing a dependency graph from package-lock.json v1 files (SC-1858)
• Added pro-only support for parsing a dependency graph from package-lock.json v2 and v3 files (SC-1991)
• The poetry.lock parser can now parse dependency relationships (ssc-1970)
• The Yarn.lock V1 and V2 parsers can parse dependency relationships. (ssc-1988)

Fixed

• The semgrep test and semgrep validate commands have been correctly documented as EXPERIMENTAL (in semgrep --help). Those commands are not GA yet and people should still use the semgrep scan --test and semgrep scan --validate (or the 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)
• Improve error handling for functionality ancillary to a scan (such as looking for nosemgrep comments and rendering autofixes) to reduce the likelihood of an unexpected error in such a component bringing down the entire scan. (saf-1737)
• Fix the behavior of semgrep when running into broken symlinks. 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)
• Fixed another crash due to exception in lines_of_file. The code 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)
• Direct dev dependencies in yarn/npm lockfiles are now correctly marked as direct (sc-1996)

1.101.0 - 2024-12-18

Added

• Improved pnpm-lock.yaml parsing. (gh-2663)

Changed

• Re-ordered some terminal output of semgrep ci to allow semgrep-app to block scans based on specific findings (SECW-2740)
• A few fields in the JSON output (e.g., "fingerprint", "metavars") require now the user to be logged in to see them.

... (truncated)

Commits

• f946d54 chore: release version 1.102.0
• bb96163semgrep/semgrep-proprietary#2849
• 708520a Dogfood: new rule to forbid the use of Fmt and ANSITerminal (semgrep/semgrep-...
• db9cac2semgrep/semgrep-proprietary#2846
• b07587dsemgrep/semgrep-proprietary#2
• 80b66dcsemgrep/semgrep-proprietary#2844
• 0401f65semgrep/semgrep-proprietary#2843
• 1d95556 cleanup: rename Matches_report.ml to Text_output.ml and unppize it (semgrep/s...
• 315f214semgrep/semgrep-proprietary#2824
• 64bf74d fix: Parse direct devDeps in in package.jsonsemgrep/semgrep-proprietary#2
• 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)

Summary by Sourcery

Build:

• Update the semgrep requirement to ~=1.102.0.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the semgrep requirement from ~=1.100.0 to ~=1.102.0, allowing the use of the latest version. This change incorporates several additions and fixes, including improved dependency graph parsing, more robust error handling, and fixes for broken symlinks and crashes.

Sequence diagram for improved error handling in Semgrep scans

sequenceDiagram
    participant User
    participant Semgrep
    participant Scanner
    participant ErrorHandler

    User->>Semgrep: Start scan
    Semgrep->>Scanner: Initialize scan

    alt Encounter broken symlink
        Scanner->>ErrorHandler: Report broken symlink
        alt Symlink is explicit scanning root
            ErrorHandler->>User: Show error
        else Symlink found during scan
            ErrorHandler->>User: Show warning
        end
    end

    alt Encounter file access issue
        Scanner->>ErrorHandler: Report lines_of_file exception
        ErrorHandler->>Scanner: Continue scan
        Note over ErrorHandler: Prevents whole scan abort
    end

    Scanner->>Semgrep: Complete scan
    Semgrep->>User: Return results

Loading

File-Level Changes

Change	Details	Files
Updated the semgrep dependency	Updated semgrep from version ~=1.100.0 to ~=1.102.0	requirements.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.