-
Notifications
You must be signed in to change notification settings - Fork 109
December release notes #2449
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
Closed
Closed
December release notes #2449
Changes from 7 commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
b5d6188
product updates slack channel updates added
abhijna f0a65d5
semgrep releases updates added
abhijna a71e496
versions released
abhijna e97d23a
semgrep app
abhijna c75aa7f
index updated
abhijna de3646f
index
abhijna 8c49e45
minor revisions
abhijna 1528249
added katie's suggestions
abhijna 84a0ee4
updated index
abhijna 56426ad
automations bullet removed
abhijna 6570580
two part sentences
abhijna 4c490d1
Update release-notes/december-2025.md
abhijna 234e5df
Update release-notes/december-2025.md
abhijna 7f88ea2
Update release-notes/december-2025.md
abhijna 9192cfa
Update release-notes/december-2025.md
abhijna b45d542
Update release-notes/december-2025.md
abhijna 0b47850
Update release-notes/december-2025.md
abhijna 8cb30e5
Update release-notes/december-2025.md
abhijna 0336893
Update release-notes/december-2025.md
abhijna d5ad690
Update release-notes/december-2025.md
abhijna 836400a
findings details
abhijna 310586d
Merge branch 'abhijna/tec-490-december-release-notes' of github.com:s…
abhijna d6baf28
index updated
abhijna 4e1555c
push a change
abhijna File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,128 @@ | ||
| --- | ||
| slug: december-2025 | ||
| hide_title: true | ||
| description: >- | ||
| Release notes include the changes, fixes, and additions in specific versions of Semgrep. | ||
| toc_max_heading_level: 3 | ||
| title: December 2025 | ||
| tags: | ||
| - Release notes | ||
| --- | ||
|
|
||
| <!-- Remember to add previous month's under-the-cut behavior --> | ||
| <!-- Remember to update index page --> | ||
|
|
||
| # Semgrep release notes for December 2025 | ||
|
|
||
| The following updates were made to Semgrep in December 2025. | ||
|
|
||
| ## 🌐 Semgrep AppSec Platform | ||
|
|
||
| ### Added | ||
| - New **Priority** tab on **Findings** page to surface high-priority findings. Each product has default priority categories, and Semgrep admins can customize the **Priority** tab to control which findings appear. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - New **Provisionally ignored** finding status. Findings marked as unreachable, invalid, or Assistant false positives move out of your default open list while remaining available for review. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - You can now link directly to a specific tab in the Admin panel, making it faster to navigate to settings. | ||
khorne3 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - New automation conditions for rules and rulesets. Automations can now trigger based on specific rule IDs or ruleset IDs, giving you more precise control over when automations run. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Commit author emails now appear in findings. When available, findings show the commit author’s email to help you quickly identify the right owner. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Admins can now save Priority tab filters for all users. Admins can save filter presets that control which findings appear in the Priority tab across the organization, making it easier to align teams on findings that matter most. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Changed | ||
| - Updated the **Findings** page with redesigned filters, improved navigation, and more intuitive links. The code path now opens the finding's **Details** page, and an in-product tour introduces the new layout. | ||
| - On the **Projects** page, project names now link directly to project details, making it easier to jump to scan information from the project list. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Easier access to ticketing integration settings. When no ticketing integration is configured, there is now a prominent link to the relevant settings page. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Updated **Settings** page layout. The **Settings** page has been reorganized to highlight commonly used features and make it easier to find what you need. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - The triage-by-comment setting is now available in the global settings section, making it easier to manage across products. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Improved visibility for social authentication after SSO setup. When SSO is enabled, the app now shows warnings for social authentication in **Settings > Access > Login** methods and highlights users using social auth in **Settings > Users**, helping admins identify and reduce security risks. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Improved SSO provisioning behavior. Newly created users who sign in with SSO are now added only to the default deployment, reducing unintended access in multi-deployment organizations. | ||
| - Clearer messages when managing authentication providers. Activating or deactivating SSO and other authentication providers now shows more user-friendly success and partial-failure messages. | ||
| - ==Improved SSO login handling for migrated identity providers. For migrated SAML and OpenID providers, Semgrep now routes logins through WorkOS, improving reliability while falling back to the existing login flow when needed.== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - The **Today** section on the **Reporting** page now uses the same priority definitions as the **Findings** page, including any custom priority settings. | ||
| - Updated **Guardrails** chart to reflect provisionally ignored findings. The **Guardrails** chart now shows Provisionally ignored findings instead of the previous **Filtered by Assistant** field, providing a more complete view of findings excluded from the default open list. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Simplified user search on the **Manage users** page. You can now search by email, username, or ID using a single search field, without selecting the search type first. | ||
|
|
||
| ### Fixed | ||
| - Fixed incorrect tab selection during navigation. The correct tab is now highlighted when viewing pages under the project path. | ||
| - Fixed IdP-initiated SAML login issues. You can now sign in successfully using IdP-initiated SAML. | ||
| - ==Fixed source code manager configuration updates to return the updated settings on validation errors.== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed Assistant triage actions for read-only users. Read-only users can no longer record agreement with Assistant analysis, and the activity timeline now reflects only actions taken by users with triage permissions. | ||
| - ==Fixed GitHub Enterprise connection setup. The Connect button now works correctly when adding a GitHub Enterprise integration.== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - ==Fixed filter action buttons appearing when no changes were made. The Save and Reset buttons now appear only when you’ve modified filters or have saved views to manage.== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - ==Fixed several issues with Findings filters and saved views. Saving and resetting filters now works correctly, time-based filters persist as expected, permissions to save filters are enforced correctly, and the Priority tab count stays accurate when saved filters change.== (redundant?) | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed CNAPP visibility for non-admin users. Users with access to findings can now see CNAPP integration status, ensuring CNAPP filters and descriptions display correctly. | ||
| - Fixed an issue where the **Users** page did not reset when changing the search query. | ||
| - Fixed an issue where the **Teams** search bar was unusable when adding users or projects. | ||
| - Fixed an issue preventing custom OpenAI API keys from being saved. | ||
| - When a scan is running, the **Analyze** button on the finding's **Details** page is now disabled with an explanatory tooltip. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed team filter visibility in the **Findings** page. Team filters now appear only when RBAC is enabled, ensuring filters reflect your deployment’s access controls. | ||
|
|
||
| ## 💻 Semgrep Code | ||
|
|
||
| ### Changed | ||
| - Git LFS objects are excluded from baseline scans. Files tracked with Git LFS are no longer scanned during baseline runs, avoiding large or binary files that are not supported by Semgrep. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Fixed | ||
| - Fixed incorrect **Fixed** statuses for files that failed to scan. Findings in files that time out or fail to scan are no longer marked as fixed, ensuring scan results more accurately reflect what was actually analyzed. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed validation failures for certain valid rules. Rules that include emoji in messages now validate correctly. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed an interfile scan timeout regression. Restored the previous default job behavior to prevent unexpected timeout changes. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed duplicate scans triggered by GitHub pull request updates. Semgrep now processes pull request update events only once, preventing duplicate scans for the same change. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - ==Fixed a rare issue where timeouts could be mishandled, which could lead to inconsistent warnings or scan behavior.== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| ## ⛓️ Semgrep Supply Chain | ||
|
|
||
| ### Added | ||
| - Advisories now show impacted projects and branches. Click an advisory to see affected projects and branches, and use quick links to jump directly to filtered findings. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Expanded Maven reachability coverage. New **High severity** reachability rules improve vulnerability detection for Java, Kotlin, and Scala projects. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Symbol analysis support for Supply Chain–only scans when calling `semgrep ci`. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Changed | ||
| - Filter dependencies by multiple license policy outcomes. The **Dependencies** page license filter now supports multi-select, so you can view dependencies that are **Allowed**, **Blocked**, or **Commented** at the same time. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| ### Fixed | ||
| - Fixed project filtering on the **Dependencies** page. Filtering by multiple projects now works as expected; the search field clears correctly after you select a project. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed symbol analysis to analyze only relevant language files per ecosystem during Supply Chain scans. | ||
| - Fixed CVE filter chip labeling for shared rules. Filter chips now show all applicable CVEs instead of only the first. | ||
| - Fixed missing findings in advisory filters. Advisory filters now correctly show all existing findings, including those created by parity rules, even after reachability rules are published. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Fixed project selection in Supply Chain filters. You can now select multiple projects as expected when filtering Supply Chain results. | ||
|
|
||
| ## 🤖 Semgrep Assistant | ||
|
|
||
| ### Added | ||
| - Cursor post-generation hook support. New MCP flags enable Semgrep to integrate with Cursor workflows after code generation. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - AI memories now include links to the pull request or merge request comments where triage decisions were made, improving traceability back to the original discussion. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| ### Changed | ||
| - ==Pull request comments for Semgrep rules now include AI-generated explanations to help developers understand findings. The summary replaces the rule message, with more details available when expanded.== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - ==Findings now include AI-generated explanations to help clarify why a rule flagged your code, with a concise summary available when applicable.== (Double check if this is just for AI detection findings) | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - Clearer error messages for Assistant analysis. Assistant notifications now show more specific error messages, helping you understand why an analysis could not run. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - ==Improved rule clarity in the AI memories view. When multiple rules share the same name, the full rule path is now shown to distinguish them, and rules are sorted to make them easier to find.== (AI detection?) | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| ### Fixed | ||
|
|
||
| ## 🔐 Semgrep Secrets | ||
|
|
||
| ### Added | ||
|
|
||
| ### Changed | ||
|
|
||
| - Semgrep Secrets findings are now assigned **Critical** severity. This applies to Secrets findings in scans performed after November 2025. Any existing findings from those rules will be updated to **Critical** after the project's next full scan. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Fixed | ||
| - Fixed a crash when configuring Slack notifications for Secrets policies. Selecting a Slack channel no longer causes the page to crash, and configurations now save successfully. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## 📝 Documentation and knowledge base | ||
|
|
||
| ### Added | ||
| - Improved API documentation for Ruleboards and Policies. Updated the API docs to correctly display request parameters in the request body and hide path parameters, making it easier to understand and use these endpoints. | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## 🔧 OSS Engine | ||
|
|
||
| ### Changed | ||
| - ==Semgrep’s Docker image now uses Alpine Linux 3.23== | ||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
abhijna marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| * The following versions of the OSS Engine were released in December 2025: | ||
| * [<i class="fas fa-external-link fa-xs"></i> 1.145.0](https://github.com/semgrep/semgrep/releases/tag/v1.145.0) | ||
| * [<i class="fas fa-external-link fa-xs"></i> 1.146.0](https://github.com/semgrep/semgrep/releases/tag/v1.146.0) | ||
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.
Uh oh!
There was an error while loading. Please reload this page.