update ci to use a single GO_VERSION setting in ci_release.yml

[ramin]

Overview

update ci to use a single GO_VERSION setting in ci_release.yml and set that version to output and uses in descendent workflows refs #16

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:

• Introduced a new "setup" job in the CI release workflow, which sets and outputs the Go version. This change enhances consistency and dependency management in the workflow.
• Updated the variable name from GO_VERSION to go-version in the lint and test workflows, ensuring uniformity across different workflows.

[coderabbitai]

Walkthrough

The changes encompass the addition of a new job in the CI release workflow to manage the Go version and its propagation to dependent jobs. Additionally, a consistency adjustment was made by renaming the GO_VERSION input variable to go-version across relevant workflows.

Changes

File Path	Summary
.github/workflows/ci_release.yml	Added a setup job to establish and output the Go version, with dependencies updated in the lint and test jobs.
.github/workflows/lint.yml .github/workflows/test.yml	Altered GO_VERSION to go-version for uniformity, ensuring consistent usage within the workflows.

🐇🍂

In the season of fall, when leaves take their flight,

CodeRabbit hops in, making everything right.

With a tweak here and there, in the moon's gentle light,

Our workflows now run with much more delight.

So here's to the changes, small and grand,

Crafted carefully by CodeRabbit's hand. 🎉🥕

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration 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]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 57bc360 and cabe74c.

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

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cabe74c and 15ccd6b.

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 (2)

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

Additional comments not posted (3)

.github/workflows/ci_release.yml (3)

27-37: The setup job is well-configured to centralize the Go version setting, ensuring consistency across workflows.

---

40-43: The lint job correctly depends on the setup job for the Go version, ensuring that it uses the centralized setting.

---

46-49: The test job correctly depends on the setup job for the Go version, ensuring that it uses the centralized setting.