sysdig-secure-3.4.1

🧪 Testing

• Track the newest and oldest supported sysdig-cli-scanner versions and run the integration tests against both, ensuring compatibility across the supported scanner range.

---

What's Changed

• feat: track newest and oldest sysdig-cli-scanner versions and test against both by @tembleking in #162
• chore: Address scanner-version-testing review feedback by @tembleking in #163

Full Changelog: sysdig-secure-3.4.0...sysdig-secure-3.4.1

sysdig-secure-3.4.0

✨ New Features

• Exposed fpkev (fixable percentage of known exploited vulnerabilities) and the CVSS temporal score from scan results.

What's Changed

• refactor: split RemoteSysdigImageScanner and enhance testing coverage by @tembleking in #158
• feat: expose fpkev and CVSS temporal score from scan results by @tembleking in #160
• chore: organize justfile into groups and switch devshell to prek by @tembleking in #161

Full Changelog: sysdig-secure-3.3.3...sysdig-secure-3.4.0

sysdig-secure-3.3.3

🐛 Bug Fixes

• Fixed a NullPointerException when processing scan results from cli-scanner >= 1.25.0.

What's Changed

• fix: NPE on scan results from cli-scanner >= 1.25.0 by @tembleking in #155

Full Changelog: sysdig-secure-3.3.2...sysdig-secure-3.3.3

sysdig-secure-3.3.2

🛡️ Security

• Fixed 4 BouncyCastle CVEs by updating dependencies.

🔧 Maintenance

• Updated Jenkins baseline and dependencies.
• Replaced Makefile with justfile for build automation.
• Added contribution guidelines.

What's Changed

• chore: update jenkins baseline, dependencies and add guidelines by @tembleking in #150
• chore: update deps, fix 4 bouncycastle CVEs, replace Makefile with justfile by @tembleking in #154

Full Changelog: sysdig-secure-3.3.1...sysdig-secure-3.3.2

sysdig-secure-3.3.1

🐛 Bug Fixes

• Respects the global evaluation result for accepted risks. Previously, if an image was accepted as a risk, the step would still fail if any policy failed. Now, the global result takes precedence.

♻️ Refactoring

• The policy representation logic has been refactored to be more extensible and maintainable.

What's Changed

• refactor(domain): Split PolicyBundleRule into interface and implementations by @tembleking in #148
• fix: respect global evaluation result for accepted risks by @tembleking in #149

Full Changelog: sysdig-secure-3.3.0...sysdig-secure-3.3.1

sysdig-secure-3.3.0

✨ New Features

• Implemented image diff functionality with UI comparison for scanning results ("Vulnerabilities added" and "Vulnerabilities fixed" tables). This provides a clear and immediate overview of how the security posture has changed between image versions, making it easier to track remediation efforts and identify newly introduced risks.

---

What's Changed

• feat: Implement image diff by @alecron in #147

New Contributors

• @alecron made their first contribution in #147

Full Changelog: sysdig-secure-3.2.0...sysdig-secure-3.3.0

sysdig-secure-3.2.0

🐛 Bug Fixing

• Fixed a deserialization error affecting the status of old Sysdig jobs in Jenkins.
  When Jenkins reloaded build data from disk, previously serialized executions failed to deserialize correctly.
  This fix restores backward compatibility so that older builds can still be opened correctly, and it also introduces a regression test to avoid similar issues in the future.

🚀 Improvements

• Removed the legacy "Policy Evaluation Summary" functionality and revamped the reporting screen with a cleaner UI, simplified filter controls, and modernized JavaScript/CSS. This also reduces code complexity and removes unused code paths.

🧪 CI / Tooling

• Added a pre-commit configuration to enforce consistent formatting and applied fixes across the codebase.

---

What's Changed

• fix: solve error deserializating status of old jobs with sysdig by @tembleking in #144
• ci: add pre-commit configuration and fix all findings by @tembleking in #145
• feat: rebump reporting screen by @tembleking in #146

Full Changelog: sysdig-secure-3.1.2...sysdig-secure-3.2.0

sysdig-secure-3.1.2

🐛 Bug Fixing

• Fixed a null pointer issue by allowing the expiration date in "accept risk" to be nullable. Remember that this requires sysdig-cli-scanner with a version at least >=1.22.4.

📦 Improvements

• Updated dependencies, including bumping io.jenkins.tools.bom:bom-2.479.x and upgrading sysdig-cli-scanner to 1.22.6.
• Banned JUnit 4 imports to ensure consistency with modern testing standards.

What's Changed

• fix: make expiration date in accept risk nullable by @tembleking in #141
• chore(deps): bump io.jenkins.tools.bom:bom-2.479.x from 4488.v7fe26526366e to 5054.v620b_5d2b_d5e6 by @dependabot[bot] in #139
• chore: update dependencies and sysdig-cli-scanner to 1.22.6 by @tembleking in #143
• Ban JUnit 4 imports by @strangelookingnerd in #142

Full Changelog: sysdig-secure-3.1.1...sysdig-secure-3.1.2

sysdig-secure-3.1.1

🐛 Bug Fixing

• Fixed a null pointer exception for v1 output format when the vulnerability has no solution date, but was fixed according to the report.

What's Changed

• fix: fix null pointer exception on solution date from report v1 by @tembleking in #140

Full Changelog: sysdig-secure-3.1.0...sysdig-secure-3.1.1

sysdig-secure-3.1.0

✨ New Features

• Added support for scan result v1 report format. This requires sysdig-cli-scanner version at least >=1.22.4

♻️ Refactoring

• Added format-independent domain model.

🎨 Code Style

• Applied automatic code formatting for consistency.

---

What's Changed

• refactor: add format-independent domain model by @tembleking in #135
• refactor: use scan result v1 report format by @tembleking in #137
• style: add code auto formatting by @tembleking in #138

Full Changelog: sysdig-secure-3.0.4...sysdig-secure-3.1.0