downgrade runner to ubuntu 22.04

[mo-c4t]

• use ubuntu 22.04 runner for building
• put the binary in a directory "camino-conduit-{version}" before packing

Summary by CodeRabbit

• Chores
  • Updated the continuous integration environment to a specific Ubuntu version, ensuring more consistent and stable builds.
  • Reorganized release artifact packaging into a version-specific directory for clearer, more streamlined deployments.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the CI workflow configurations to use Ubuntu 22.04 instead of the latest Ubuntu version. Both the CI and release workflows now specify the new operating system for the build_docker and build_binary jobs. Additionally, the release workflow modifies the binary packaging process by creating a version-specific subdirectory before compressing the artifact.

Changes

Files Affected	Change Summary
.github/workflows/ci.yml and .github/workflows/release.yml	Updated runs-on attribute in build_docker and build_binary jobs from ubuntu-latest to ubuntu-22.04.
.github/workflows/release.yml	Modified the build_binary job:

• Creates a version-tagged directory under ./build
• Copies binary into the new directory
• Compresses the directory into a tarball |

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Runner
    participant Job as BuildBinary Job
    CI->>Job: Trigger binary build job
    Job->>Job: Create version-specific directory (camino-conduit-<tag>)
    Job->>Job: Copy binary into directory
    Job->>Job: Compress directory into tarball
    Job-->>CI: Return packaged artifact

Loading

Possibly related PRs

• Binary #2: Updates the CI job environment specification for build_docker and build_binary, closely aligning with these modifications.
• Build script #3: Involves similar changes in the environment setup and binary packaging process in the CI workflow.

Suggested reviewers

• evlekht
• Noctunus

Poem

I'm a rabbit with a hop so bright,
Ubuntu 22.04 now takes the spotlight.
CI flows smooth with a brand new vibe,
Packaging binaries in a versioned tribe.
Code and carrots, both a delight—
Hoppin' forward into the night!

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/release.yml (1)

43-45: Organize Binary Packaging into Version-Specific Directory
The commands create a directory named camino-conduit-${{ github.event.release.tag_name }} within the build directory, copy the binary into it, and then package it. This restructuring meets the objective of organizing the output binary effectively.

Consider adding a check to verify that ./build/camino-conduit exists before copying, to prevent potential errors if the build step fails. Additionally, wrapping file paths in quotes (e.g., "./build/camino-conduit-${{ github.event.release.tag_name }}") could help avoid issues with unexpected spaces in the version tag, though such cases may be rare.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4d46b5a and 6087df6.

📒 Files selected for processing (2)

• .github/workflows/ci.yml (2 hunks)
• .github/workflows/release.yml (2 hunks)

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

• .github/workflows/ci.yml

🔇 Additional comments (2)

.github/workflows/release.yml (2)

13-13: Update Runner for Build Docker Job
The runs-on: ubuntu-22.04 setting is correctly applied, ensuring that the Docker build job runs in the desired environment as per the PR objectives.

---

35-35: Update Runner for Build Binary Job
The change from ubuntu-latest to ubuntu-22.04 guarantees consistent build conditions for the binary job, aligning perfectly with the specified PR changes.