Today, we are excited to announce the release of JiHu GitLab 15.10 with the ability to automatically resolve SAST findings when rules are disabled, a new view to see all branch-related settings together, the ability to create and switch branches in the Web IDE Beta, compliance frameworks reports, and much more!

These are just a few highlights from the 115+ improvements in this release. Read on to check out all of the great updates below.

We thank the wider JiHu GitLab community for the 170+ contributions they provided to JiHu GitLab 15.10! At JiHu GitLab , everyone can contribute and we couldn't have done it without you!

To preview what's coming in next month’s release, check out our Upcoming Releases page, which includes our 15.11 release kickoff video.

GitLab SAST now automatically resolves vulnerabilities from the Semgrep- and KICS-based analyzers when either:

• You disable a predefined rule.
• We remove a rule from the default ruleset.

This change helps you focus on the vulnerabilities that are still relevant after the rule update. Previously, when a rule was no longer scanned, its findings would be marked “No longer detected” but you still had to take action to resolve them. Now, the Vulnerability Management system automatically resolves those findings and leaves a comment explaining that the rule was removed, so you still have a historical record of the vulnerability.

This change will automatically resolve findings from a small number of rules that we’ve replaced or removed in recent releases. In this release, we’ve also removed a JavaScript SAST rule that created too many false-positive results.

This feature is enabled by default on GitLab.com and in GitLab 15.10. On GitLab.com, contact Support if you need to disable the flag for your project. On GitLab self-managed, you can disable the project-level feature flag named sec_mark_dropped_findings_as_resolved.