ci: Change 'ubuntu-latest' runners to 'ubuntu-22.04'

[mertssmnoglu]

Change ubuntu-latest runners to ubuntu-22.04 because ubuntu-latest runners will point to 24.04 soon.

Ref

• Ubuntu-latest workflows will use Ubuntu-24.04 image actions/runner-images#10636
• https://github.com/bluewave-labs/capture/actions/runs/12454911902

Summary by CodeRabbit

• Chores
  • Updated the linting and release workflows to use Ubuntu 22.04 for job execution environments.

[coderabbitai]

Walkthrough

The pull request involves updating the GitHub Actions workflow configurations for both linting and release processes. Specifically, the changes modify the runs-on attribute in two workflow files (.github/workflows/lint.yml and .github/workflows/release.yml) from ubuntu-latest to ubuntu-22.04. This update ensures a more precise specification of the Ubuntu operating system version for job execution environments while maintaining the existing workflow steps and configurations.

Changes

File	Change Summary
.github/workflows/lint.yml	Updated job environment from ubuntu-latest to ubuntu-22.04
.github/workflows/release.yml	Updated release job environment from ubuntu-latest to ubuntu-22.04

Possibly related PRs

• CI/CD: Release Pipeline with GoReleaser #24: Similar update of runs-on attribute from ubuntu-latest to ubuntu-22.04 in release job configuration

Suggested reviewers

• ajhollid

Poem

🐰 Workflows dancing with precision,
Ubuntu versions in smooth transition,
From latest to twenty-two-point-oh,
Our CI/CD pipeline starts to glow!
Rabbit's runtime, now crystal clear 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 861c26c and b73bf1e.

📒 Files selected for processing (2)

• .github/workflows/lint.yml (1 hunks)
• .github/workflows/release.yml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/lint.yml

🔇 Additional comments (2)

.github/workflows/release.yml (2)

16-16: LGTM! Good proactive change to prevent future issues.

The change from ubuntu-latest to ubuntu-22.04 is a good preventive measure, ensuring workflow stability when ubuntu-latest transitions to ubuntu-24.04.

---

Line range hint 25-27: Critical: Invalid Go version specified

The specified Go version 1.23.1 is incorrect as it doesn't exist. The latest stable version of Go is 1.21.x.

Apply this fix:

        uses: actions/setup-go@v5
        with:
-          go-version: 1.23.1
+          go-version: 1.21.5

Let's verify the latest Go version:

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.