[Snyk] Security upgrade ruby from 3.4.5-slim to 3.4.9-slim

[Bulletdev]

Snyk has created this PR to fix 3 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

• Dockerfile.production

We recommend upgrading to ruby:3.4.9-slim, as this image has only 45 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	CVE-2025-69421 SNYK-DEBIAN13-OPENSSL-15123186	614
	CVE-2025-69421 SNYK-DEBIAN13-OPENSSL-15123186	614
	CVE-2025-69421 SNYK-DEBIAN13-OPENSSL-15123186	614
	CVE-2026-28388 SNYK-DEBIAN13-OPENSSL-15969320	436
	CVE-2026-31790 SNYK-DEBIAN13-OPENSSL-15969323	436

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[supabase]

This pull request has been ignored for the connected project nnqfvgnvemqctjfhadhz because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[github-actions]

📦 Dependency Security Check

✅ No known vulnerabilities found.

View Report

No vulnerabilities found

[github-actions]

🔒 Brakeman Security Scan

• Total warnings: 0
• High confidence: 0

✅ No high confidence issues found.

[github-actions]

🔍 Semgrep Static Analysis

Severity	Count
Errors	0
Critical (HIGH confidence)	0
Warnings	2

⚠️ Warnings found (non-blocking).

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[github-actions]

🔐 Security Scan Summary

Static Analysis (SAST)

Check	Status
Brakeman	✅ success
Dependencies	✅ success
Semgrep	✅ success
Secrets	✅ success

Dynamic Analysis (DAST)

Check	Status
SSRF Protection	✅ success
Authentication	✅ success
SQL Injection	✅ success

✅ All security checks passed!

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.