Plumber 1.3

We’re thrilled to announce the launch of Plumber 1.3:

🛡️ Stronger, safer, and more resilient analyses

This release focuses on improving the resilience of the analysis process, with a refactored worker architecture, sensitive data redaction in logs, and several refinements across the platform.

🎛️ Refactored Analysis Process

We reforged the way analyses are performed by workers to make them significantly more robust against real-world failures.

What changed:

• Resilient to worker failures: If a worker crashes or restarts mid-analysis, the analysis keeps going
• Resilient to network failures: Transient network issues no longer compromise an entire analysis
• Resilient to GitLab failures: Temporary GitLab outages or errors are handled gracefully
• Guaranteed completion: An analysis always completes, even when some projects cannot be analyzed (failures are reported per project instead of failing the whole run)

The result is a much smoother experience at scale, especially for large portfolios where partial failures used to fail an entire analysis.

🔒 Redacted Sensitive Data in Logs

Plumber now automatically redacts sensitive data (tokens, keys, and other secrets) from its logs. This reduces the risk of secret exposure when sharing logs for debugging or support.

What you get:

• Automatic redaction: Tokens, keys, and other secrets are masked in logs by default
• Safer troubleshooting: Share logs with confidence, without leaking credentials

⚙️ Minor Updates

• Security: Resolved package CVEs for enhanced security
• Fix: Various bug fixes and stability improvements
• UX improvements: Various UX enhancements across the platform
• Feedback button: Users on a free license can now submit feedback directly from the platform. Your input helps us prioritize what to build next.
• Issues: Adjust criticity of some issues
• Fix: Improve query to get CI/CD file content from GitLab