refactor: update Go base image to 1.22 and streamline Dockerfile inst…

[SharanRP]

refactor

Summary by CodeRabbit

• Chores
  • Updated the Docker build process to use a newer Go base image and simplified the source code copying steps for improved efficiency.

[coderabbitai]

Walkthrough

The Dockerfile was updated to use Go version 1.22-alpine as the build stage base image. The file copy steps were consolidated, removing the separate copying of dependency files and the redundant second source copy. The rest of the Dockerfile, including build and metadata instructions, was unchanged.

Changes

File(s)	Change Summary
Dockerfile	Updated Go base image to 1.22-alpine; simplified copy steps; removed redundancy

Poem

In Docker’s burrow, things are neat,
With Go 1.22, a tidy feat.
No more double hops for code to land,
Just one swift leap, as rabbits planned.
Dependencies bundled, the build is bright,
Hopping forward, everything’s light! 🐇✨

---

🪧 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

Dockerfile (2)

2-2: Review Go base image upgrade
Upgrading the build stage to golang:1.22-alpine is good to stay on the latest Go release, but consider pinning to a specific digest for reproducible builds and auditing.

You can lock the image to a digest like so:

- FROM golang:1.22-alpine AS builder
+ FROM golang@sha256:<digest> AS builder

---

10-11: Optimize layer caching for Go dependencies
Copying the entire context upfront busts the module-download cache on any file change. Reintroducing a two-step copy (go.mod/go.sum first, then the rest) will dramatically speed up rebuilds.

Apply this diff:

- # Copy source code (includes go.mod and go.sum)
- COPY . .
+ # Copy go.mod and go.sum separately for caching
+ COPY go.mod go.sum ./
+ RUN go mod download
+
+ # Copy the rest of the source code
+ COPY . .

Additionally, ensure you have a .dockerignore to exclude files like .git and local config from the build context.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6334c06 and ff33212.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)