use a setup job to set a go-version output and use throughout CI

[ramin]

Overview

use a setup job to set a go-version output and use throughout CI

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Chores
  • Updated CI/CD workflows for better consistency and dependency management.
• Style
  • Improved code readability and consistency in GitHub Actions workflow files.

[coderabbitai]

Walkthrough

The changes primarily focus on improving the consistency and structure of GitHub Actions workflows. A new job "setup" is introduced in the ci_release.yml workflow, and the input variable GO_VERSION is renamed to go-version in the lint.yml and test.yml workflows. These modifications enhance the readability and maintainability of the codebase.

Changes

File Path	Summary
.github/workflows/ci_release.yml	Introduced a new job "setup" that sets and outputs the GO_VERSION environment variable. The "lint" and "test" jobs now depend on the "setup" job and use its output.
.github/workflows/lint.yml, .github/workflows/test.yml	Renamed the input variable GO_VERSION to go-version for consistency. Minor changes include fixing indentation and updating comments.

Poem

🍂 As autumn leaves gently fall, 🍁

In the world of code, we stand tall. 🐇

With each commit, a new dawn, 🌅

A cleaner codebase is born. 🎉

From GO_VERSION to go-version we leap, 🔄

In the realm of workflows, changes we reap. 🌾

So here's to the devs, in all their might, 💪

Coding away, into the night. 🌙

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Note: For conversation with the bot, please use the review comments on code diffs or files.

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.json

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 652a881 and a7fd301.

Files selected for processing (3)

• .github/workflows/ci_release.yml (1 hunks)
• .github/workflows/lint.yml (2 hunks)
• .github/workflows/test.yml (4 hunks)

Files skipped from review due to trivial changes (3)

• .github/workflows/ci_release.yml
• .github/workflows/lint.yml
• .github/workflows/test.yml