[Snyk] Security upgrade golang from latest to 1.22rc2-bookworm

[mukul-kr]

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 golang:1.22rc2-bookworm, as this image has only 80 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:

Severity	Issue	Exploit Maturity
	Out-of-bounds Write SNYK-DEBIAN12-GLIBC-6210098	No Known Exploit
	Out-of-bounds Write SNYK-DEBIAN12-GLIBC-6210098	No Known Exploit
	Out-of-bounds Write SNYK-DEBIAN12-GLIBC-6210098	No Known Exploit
	Out-of-bounds Write SNYK-DEBIAN12-GLIBC-6210098	No Known Exploit
	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:

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

Summary by CodeRabbit

• Chores
  • Updated the Docker base image to golang:1.22rc2-bookworm for improved performance and security.

[coderabbitai]

Walkthrough

The Dockerfile has been updated to use a newer version of the Go programming language, specifically changing the base image from the latest general version to a more specific, pre-release version 1.22rc2-bookworm. This change suggests a need for the features or improvements available in this newer version of Go, possibly for compatibility or performance reasons.

Changes

File	Change Summary
Dockerfile	Updated base image from golang:latest to golang:1.22rc2-bookworm

🐰✨
In the realm of code, a small hop we take,
From the vast latest sea to 1.22rc2-bookworm lake.
With each line we draw, a future we make,
Crafting with care, for progress' sake.
🌟🐇

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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.
• 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 from git 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

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 94ae22b and 194bd44.

Files selected for processing (1)

• Dockerfile (1 hunks)

Additional comments: 1

Dockerfile (1)

• 1-1: The base image has been updated to golang:1.22rc2-bookworm to address security vulnerabilities. Ensure that this version is compatible with the project's dependencies and does not introduce breaking changes.