Releases: runtimeverification/llvm-backend
Releases · runtimeverification/llvm-backend
v0.1.8
Set Version: 0.1.8
v0.1.7
Set Version: 0.1.7
v0.1.6
Set Version: 0.1.6
v0.1.5
Fix usage of github PR SHA in release job (#1041) This was an oversight when refactoring the release workflow code last week; it's not easy to test this step without creating spurious PRs on the K repo so it got missed. It being missed produced a [failure](https://github.com/runtimeverification/k/actions/runs/8943558614/job/24594103312?pr=4312) in the LLVM backend update job. The fix is to send the correct version information from the stashed version file to the devops job, rather than the Git SHA as we were previously doing. --------- Co-authored-by: devops <[email protected]>
v0.1.4
Replace `LLVMREwriteEvent` with `llvm_rewrite_event` (#1040) A simple PR to modify the CamelCase in `AST.cpp` to snake_case! --------- Co-authored-by: devops <[email protected]>
v0.1.3
Build debian package (#1036) This PR sets up a Debian package build for the LLVM backend, such that we will be able to adapt the K CI testing process to download this released version rather than rebuilding the backend from scratch on every run. The package building step is tested in CI, and I have tested the part of the workflow that deals with _uploading_ the released package locally by creating and deleting releases on pushes to this branch. I'll make sure to babysit the release to ensure that the file is attached correctly when this PR is merged. The Debian packaging specifics in this PR have been largely adapted from the main K repo. --------- Co-authored-by: devops <[email protected]>
v0.1.2: Check out code when creating a release (#1037)
This was a small oversight in #1034; we should have been checking out the repo's code to get access to `package/version`. Will fix the release build when merged. --------- Co-authored-by: devops <[email protected]>