chore(deps): update helm release redis from 19.4.0 to ~19.5.0 (helm/defectdojo/chart.yaml)

[renovate]

This PR contains the following updates:

Package	Update	Change
redis (source)	minor	~19.4.0 -> ~19.5.0

---

Release Notes

bitnami/charts (redis)

v19.5.0

• [bitnami/redis] Enable PodDisruptionBudgets (#​26355)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	✅	0 findings
Sensitive Files Analyzer	✅	0 findings
AppSec Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective.

Summary:

The changes in this GitHub Pull Request primarily involve updates to the Helm chart configuration for the DefectDojo application. The key changes include updating the Redis dependency version from ~19.4.0 to ~19.5.0 in the Chart.yaml file, and updating the versions of the postgresql and redis dependencies in the Chart.lock file.

From an application security perspective, these changes do not appear to introduce any obvious security concerns. Updating dependencies to their latest versions is generally a good practice, as it can help address known security vulnerabilities. However, it's important to thoroughly test the application after any dependency update to ensure that the changes do not introduce any new issues or break existing functionality.

Additionally, it's a good idea to periodically review the dependencies and their versions to ensure they are up-to-date and to identify any potential security risks. Automated tools or services that can help with dependency management and security scanning can be valuable in this process.

Files Changed:

1. helm/defectdojo/Chart.yaml:

   • The Redis dependency version has been updated from ~19.4.0 to ~19.5.0.

2. helm/defectdojo/Chart.lock:

   • The version of the postgresql dependency has been updated from 15.5.0 to 15.5.1.
   • The version of the redis dependency has been updated from 19.4.0 to 19.5.0.
   • The digest value and generated timestamp have been updated.

Powered by DryRun Security

[mtesauro]

Approved