Skip to content

Releases: runtimeverification/llvm-backend

v0.1.8

08 May 22:10
Compare
Choose a tag to compare
Set Version: 0.1.8

v0.1.7

08 May 17:03
Compare
Choose a tag to compare
Set Version: 0.1.7

v0.1.6

07 May 11:30
Compare
Choose a tag to compare
Set Version: 0.1.6

v0.1.5

06 May 10:10
8d4130e
Compare
Choose a tag to compare
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

03 May 18:50
05c38eb
Compare
Choose a tag to compare
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

30 Apr 16:14
d7fb8af
Compare
Choose a tag to compare
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)

26 Apr 18:42
6a6c288
Compare
Choose a tag to compare
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]>