chore: bump to go 1.22.7

[fmorency]

Summary by CodeRabbit

• New Features

  • Upgraded the Go programming language version from 1.22.5 to 1.22.7 across multiple workflows and module files, enhancing compatibility and potentially improving performance and security.

• Bug Fixes

  • The update may include bug fixes and improvements from the newer Go version, ensuring a more stable environment for builds and tests.

[coderabbitai]

Walkthrough

The pull request includes updates to the Go version in multiple GitHub Actions workflow configuration files and the go.mod files. The version has been incremented from 1.22.5 to 1.22.7, reflecting a consistent upgrade across various workflows and modules. This change aims to ensure that the build and testing processes utilize the latest Go enhancements while maintaining the overall structure and logic of the workflows.

Changes

Files	Change Summary
.github/workflows/build.yml	Updated GO_VERSION from 1.22.5 to 1.22.7
.github/workflows/codeql.yml	Updated GO_VERSION from 1.22.5 to 1.22.7
.github/workflows/e2e.yml	Updated GO_VERSION from 1.22.5 to 1.22.7
.github/workflows/release-bin.yaml	Updated go-version from 1.22.5 to 1.22.7
.github/workflows/simulation.yml	Updated GO_VERSION from 1.22.5 to 1.22.7
.github/workflows/test.yml	Updated GO_VERSION from 1.22.5 to 1.22.7
go.mod	Changed Go version from 1.22.5 to 1.22.7
interchaintest/go.mod	Changed Go version from 1.22.5 to 1.22.7

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHubActions
    participant Go

    Developer->>GitHubActions: Push changes
    GitHubActions->>Go: Build with GO_VERSION 1.22.7
    Go-->>GitHubActions: Build successful
    GitHubActions-->>Developer: Notify build status

Loading

Poem

🐰 In fields of code where bunnies play,
We hop with joy, it's a bright new day!
Go's version has leaped, oh what a sight,
From 1.22.5 to 1.22.7—a delight!
With every update, our code will thrive,
Hopping along, keeping our dreams alive! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8054b9a and f7b845e.

Files ignored due to path filters (1)

• go.work is excluded by !**/*.work

Files selected for processing (8)

• .github/workflows/build.yml (1 hunks)
• .github/workflows/codeql.yml (1 hunks)
• .github/workflows/e2e.yml (1 hunks)
• .github/workflows/release-bin.yaml (1 hunks)
• .github/workflows/simulation.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)
• go.mod (1 hunks)
• interchaintest/go.mod (1 hunks)

Files skipped from review due to trivial changes (6)

• .github/workflows/build.yml
• .github/workflows/codeql.yml
• .github/workflows/e2e.yml
• .github/workflows/simulation.yml
• go.mod
• interchaintest/go.mod

Additional comments not posted (2)

.github/workflows/test.yml (1)

13-13: LGTM!

The change to the GO_VERSION environment variable is a minor version bump, which aligns with the PR objective of upgrading to Go 1.22.7. This change is unlikely to introduce any breaking changes or compatibility issues and could potentially enhance the build and test processes.

The AI-generated summary also indicates that this change is part of a consistent upgrade across various workflows and modules, which further supports the validity of this modification.

.github/workflows/release-bin.yaml (1)

23-23: LGTM!

Updating the Go version to 1.22.7 in the workflow configuration is a good practice to ensure the build process leverages the latest improvements and bug fixes.

---

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>, please review it.
  -- 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 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 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 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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.74%. Comparing base (8054b9a) to head (f7b845e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #96      +/-   ##
==========================================
+ Coverage   76.63%   76.74%   +0.11%     
==========================================
  Files          34       34              
  Lines        1802     1802              
==========================================
+ Hits         1381     1383       +2     
+ Misses        328      327       -1     
+ Partials       93       92       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.