chore: debug pipeline

[nicotsx]

Summary by CodeRabbit

• Refactor
  • Streamlined naming conventions for Linux build artifacts.
• Chores
  • Temporarily disabled building for macOS-aarch64 to focus on core platforms.

[coderabbitai]

Walkthrough

The changes reflect a simplification of the build process for a CLI tool named runtipi-cli. The naming convention for the Linux artifacts has been streamlined by removing the .tar.gz extension. Additionally, the build process for the macOS-aarch64 platform has been commented out, indicating a temporary or permanent cessation of support for that platform. The version naming for the artifacts has been kept consistent.

Changes

File Path	Change Summary
.github/workflows/build.yml	Removed .tar.gz from Linux artifact names. Commented out macOS-aarch64 build steps. Ensured consistent artifact version naming.

🐇✨
To the code we hop, make changes nonstop,
Tarballs we drop, as versions pop.
No more macOS build, in comments it's stilled,
Yet 'runtipi-cli' will be brilliantly filled.
✨🐇

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @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.
• 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.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b4720c1 and 991579b.

Files selected for processing (1)

• .github/workflows/build.yml (2 hunks)

Additional comments: 5

.github/workflows/build.yml (5)

• 21-21: Renaming the artifact to remove the .tar.gz extension is a significant change. Ensure that downstream systems that consume these artifacts are aware and can handle artifacts without the .tar.gz extension.
• 31-36: Commenting out the macOS-aarch64 build steps effectively removes this build target from the CI pipeline. Confirm that this is intentional and that stakeholders are aware of the implications of this change.
• 65-65: The dynamic naming convention for artifacts using matrix variables is a good practice for maintainability and clarity. However, ensure that the new naming convention is documented and understood by all team members and that any scripts or systems that depend on the artifact names are updated accordingly.
• 59-59: The command to create the tarball no longer includes the .tar.gz extension. This is consistent with the renaming of the artifacts. However, verify that the actual packaging of the artifacts still results in a gzipped tarball, as the command used (tar czvf) implies compression.
• 100-100: The files pattern in the release job uses a wildcard to match artifacts. Ensure that this pattern correctly matches the new artifact names without the .tar.gz extension.