ci: update release workflow

[maschad]

Summary by CodeRabbit

• Chores
  • Improved artifact upload process in release workflow to better handle different operating systems.

[coderabbitai]

Walkthrough

The artifact upload step in the release workflow was updated to use an explicit conditional to select the correct executable path based on the operating system. This replaces a wildcard pattern with a direct check for Windows or Unix-style executables during the build process.

Changes

File(s)	Change Summary
.github/workflows/release.yaml	Modified artifact upload step to conditionally select the executable path based on the OS, removing wildcard usage.

Possibly related PRs

• ci: add release workflow for aarch64 and others #14: Expands the build matrix and modifies artifact naming and packaging for multiple architectures, also involving changes to the release workflow's artifact handling.

Poem

Hopping through workflows, I see
A path split for Windows and Unix-y!
No more wildcards, just clear direction—
Each OS now gets its own selection.
With paws on the pipeline, I cheer with glee,
For artifacts found as they’re meant to be! 🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.yaml (1)

77-77: Quote conditional path expression for YAML safety
The interpolation contains characters like : and logical operators that can be misparsed by YAML. Wrap the entire expression in quotes to ensure it’s treated as a single string.

-          path: ${{ matrix.os == 'windows-latest' && format('target/{0}/release/junkanoo.exe', matrix.target) || format('target/{0}/release/junkanoo', matrix.target) }}
+          path: "${{ matrix.os == 'windows-latest' && format('target/{0}/release/junkanoo.exe', matrix.target) || format('target/{0}/release/junkanoo', matrix.target) }}"

Would you like an example of splitting this into two upload steps (one for Windows, one for Unix) to improve readability?

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 90ea455 and a6396fd.

📒 Files selected for processing (1)

• .github/workflows/release.yaml (1 hunks)