ci: Set Docker Workflow to use Go 1.22

[CharlieMc0]

Description

The workflow to push images to docker is not working and needs to be set to use Go 1.22.
https://github.com/zeta-chain/node/actions/runs/10408541357

How Has This Been Tested?

Summary by CodeRabbit

• New Features
  • Enhanced GitHub Actions workflow to support Go programming environment with version 1.22.2.
  • Added a verification step to check the installed Go version.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Walkthrough

The recent modifications enhance the GitHub Actions workflow by incorporating the Go programming environment setup. By adding the actions/setup-go@v5 action with a specified Go version (1.22.2), the workflow ensures that Go-related tasks can be executed effectively. Additionally, a verification command is included to confirm the successful installation of Go, thereby improving the reliability and functionality of the CI/CD process.

Changes

File Path	Change Summary
.github/workflows/docker-build-and-push.yml	Added uses: actions/setup-go@v5 with go-version: '1.22.2' and included run: go version for verification.

Sequence Diagram(s)

sequenceDiagram
    participant CI as GitHub Actions
    participant GoSetup as Setup Go Environment
    participant Verify as Verify Installation

    CI->>GoSetup: Setup Go version 1.22.2
    GoSetup-->>CI: Go environment configured
    CI->>Verify: Run command to check Go version
    Verify-->>CI: Confirm successful setup

Loading

---

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 testing code 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 testing code 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 testing code.
  • @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.

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 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

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.

[gartnera]

This is the go version outside the docker build. Per the errors you need to set the go version inside the docker build.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7039dcc and 422b2bd.

Files selected for processing (1)

• .github/workflows/docker-build-and-push.yml (2 hunks)

Additional comments not posted (2)

.github/workflows/docker-build-and-push.yml (2)

32-35: Go setup and verification are correctly implemented.

The inclusion of actions/setup-go@v5 with a specific version ensures consistency across builds. The go version command effectively verifies the installation.

---

69-72: Go setup and verification are correctly implemented.

The use of actions/setup-go@v5 with a specified version ensures that the build environment is consistent. The go version command is a good practice to confirm the setup.