2025.2.0
Release Date: February 20, 2025
System Requirements Update
Ensure your infrastructure meets the latest requirements for optimal performance and security:
| Component | Minimum Version | Recommended Version |
|---|---|---|
| KOTS | 1.117.3 | Latest |
| Kubernetes | 1.25 | 1.30 |
| PostgreSQL | 15 | 16 |
| Redis | 6 | 7 |
Helm & Upgrade Considerations
To ensure compatibility, please review Helm values updates from the previous version.
Air gap deployment? Find all the images and tag names in the air gap install page.
Search Incidents by Secret Value
GitGuardian allows you to monitor secret leaks across thousands of your repositories and over 30 different types of sources. It is reassuring to know that this critical secret, which provides access to your corporate LDAP, has not been detected anywhere.
Bitbucket Cloud Scanning
Secure your Bitbucket Cloud repositories with secrets detection powered by GitGuardian.
- Detect exposed credentials and secrets in real-time.
- Gain visibility into security incidents directly in your dashboard.
Learn more
Custom Tags Early Access
Improve incident organization and tracking with Custom Tags, allowing users to filter, sort, and categorize incidents more effectively. For now, custom tag management (CRUD) and tag assignments to incidents can only be done via the API (API documentation), with UI support coming soon.
To activate this feature, enable custom_tags_enabled in the Preferences page.
Autoscaling
HPA now supports web applications (e.g., webapp-public_api), allowing automatic scaling based on demand for improved performance and resource efficiency. Learn more on the autoscaling page.
Secrets Detection Engine (v2.131)
Bringing enhanced accuracy and broader coverage:
- New Detectors
- Improved Detection for GitHub Tokens
- Enhanced validation for GitHub Enterprise Token
- Refined rules for various GitHub authentication tokens:
Enhancements
- Scan Only Addition Lines in Commits: Now, when using ggshield or our check runs integration, we only scan for added lines in commits. Developers will no longer be blocked while remediating incidents.
- Jira Issue Tracking Integration: Added support for "Numbers (or float)" and "Group Pickers (single group)" custom fields in Jira templates, allowing more customization in notifications and issue tracking.
- Enhanced Email Incident Alerting Controls for Members: You can now manage email notification settings more effectively with an option that allow updates through the API, and customize account-level defaults, ensuring a more tailored communication experience for all members. Learn more
Fixes
- Sources:
- Azure Repos Integration: Fixed an issue where organization deletions were not properly synced when using ADO installations in Organization-mode.
- GitLab Integration: Resolved an issue where GitLab installations were incorrectly revoked due to temporary plan downgrades or admin status changes.
- Users & Teams:
- Incidents: Resolved an issue where restricted users could not view the Vulnerable Sources block.
- Users: Resolved an issue where user deletion was prevented due to the presence of saved views associated with the user.
- Teams Management: Resolved an issue where action menus were not displayed in the teammates table for non-admin users in certain cases.
- Alerting:
- Confluence Cloud Integration: Fixed an issue where some Confluence Cloud events without a spaceKey were incorrectly ignored.
- PagerDuty Alerts for Security Incidents: Fixed an issue where the integration was not sending alerts for real-time incidents.
- Email Notifications: Fixed an issue where emails for ignored and valid incidents were sent to all teams a user belongs to, instead of only the teams managing the affected repository.
- Self-Hosted:
- Helm: Fixed an issue where connecting to Redis Sentinel failed when using a password with special characters.
- Kots: Restore the left navigation menu in the KOTS admin console for embedded cluster installations.
