Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: check that LLVM branch corresponds to semver before releasing #124

Conversation

antonbaliasnikov
Copy link
Contributor

What ❔

Check LLVM.lock branch corresponds to semver before releasing.

Why ❔

To make sure LLVM version is pinned to LLVM backend release instead of main.

Checklist

  • PR title corresponds to the body of PR.
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via cargo fmt and checked with cargo clippy.

@antonbaliasnikov antonbaliasnikov force-pushed the abalias-cpr-1828-add-a-check-that-llvmlock-contains-semver-upon-release branch from a44b1cd to b0289a2 Compare November 13, 2024 17:26
Copy link

codecov bot commented Nov 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.12%. Comparing base (9c8fd92) to head (b0289a2).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##           main     #124       +/-   ##
=========================================
+ Coverage      0   64.12%   +64.12%     
=========================================
  Files         0       54       +54     
  Lines         0     4365     +4365     
=========================================
+ Hits          0     2799     +2799     
- Misses        0     1566     +1566     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@antonbaliasnikov antonbaliasnikov merged commit 602b990 into main Nov 15, 2024
11 checks passed
@antonbaliasnikov antonbaliasnikov deleted the abalias-cpr-1828-add-a-check-that-llvmlock-contains-semver-upon-release branch November 15, 2024 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants