proxybroker2 [Snyk] Security upgrade python from 3.9-slim to 3.13.0a3-slim

This PR was automatically created by Snyk using the credentials of a real user.

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

Changes included in this PR

Dockerfile

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

Some of the most important vulnerabilities in your base image include:

Priority Score / 1000	Issue	Exploit Maturity
221	CVE-2024-22365 SNYK-DEBIAN12-PAM-6178914	No Known Exploit
221	CVE-2024-22365 SNYK-DEBIAN12-PAM-6178914	No Known Exploit
221	CVE-2024-22365 SNYK-DEBIAN12-PAM-6178914	No Known Exploit
150	Use After Free SNYK-DEBIAN12-SQLITE3-6155400	No Known Exploit
500	Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963	No Known Exploit

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

🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Use After Free

Summary by CodeRabbit

Chores
- Updated the Python base image to version 3.13.0a3-slim for improved performance and security.

Feb 06 '24 01:02 bluet

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Feb 06 '24 01:02 sonarqubecloud[bot]

Walkthrough

The update involves upgrading the Python base image used in the Dockerfile from version 3.9-slim to the alpha version 3.13.0a3-slim. This change suggests an effort to leverage the latest Python features, improvements, or security patches, indicating a forward-looking approach to maintaining the project.

Changes

File	Change Summary
Dockerfile	Updated Python base image from `3.9-slim` to `3.13.0a3-slim`

🐇✨
In the Dockerfile's cozy nook,
A change was made, a bold step took.
From 3.9 to 3.13's alpha gleam,
A leap through versions, a coder's dream.
🚀🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>.
- Generate unit-tests for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit tests for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai generate interesting stats about this repository and render them as a table.
- @coderabbitai show all the console.log statements in this repository.
- @coderabbitai read src/utils.ts and generate unit tests.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
The JSON schema for the configuration file is available here.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json