Skip to content

fix: run version checks on native release targets - #8

Merged
ygpark80 merged 1 commit into
mainfrom
fix/native-version-check
Aug 10, 2026
Merged

fix: run version checks on native release targets#8
ygpark80 merged 1 commit into
mainfrom
fix/native-version-check

Conversation

@ygpark80

@ygpark80 ygpark80 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

User description

Changes

  • execute compiled cvlt --version checks only on native runner targets
  • keep cross-compiled ARM64 Linux and x64 macOS artifacts in the build/package matrix

Testing

  • actionlint .github/workflows/release.yml
  • confirmed the failed release reached cvlt --version and failed with Exec format error, not a version mismatch

CodeAnt-AI Description

Run release version checks only on runners that can execute the built binary

What Changed

  • Skips cvlt --version execution for cross-compiled Linux ARM64 and macOS x64 release artifacts
  • Continues validating the version for release targets built on compatible native runners
  • Keeps cross-compiled artifacts in the release build matrix without failing on execution-format errors

Impact

✅ Fewer release failures for cross-compiled artifacts
✅ Reliable version validation on native targets
✅ ARM64 Linux and x64 macOS releases remain available

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@codeant-ai

codeant-ai Bot commented Aug 10, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 96f8dde Aug 10, 2026 · 08:18 08:18

@codeant-ai

codeant-ai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Aug 10, 2026
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@ygpark80, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 seconds

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 840ac636-2871-470b-80b9-41e1140f32a9

📥 Commits

Reviewing files that changed from the base of the PR and between 3d8c7a2 and 96f8dde.

📒 Files selected for processing (1)
  • .github/workflows/release.yml

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

Comment @coderabbitai help to get the list of available commands.

@ygpark80
ygpark80 merged commit e3b5a0e into main Aug 10, 2026
2 checks passed
@ygpark80
ygpark80 deleted the fix/native-version-check branch August 10, 2026 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant