Commit Graph

10 Commits

Author SHA1 Message Date
youben11
f6edcd28e9 ci: release linux python wheels with cuda support 2023-01-13 11:43:05 +01:00
youben11
9c370e1cec ci: fix macos release tarball 2023-01-12 17:56:53 +01:00
David Testé
af265206a9 chore(ci): move macos build and release jobs to their own workflow 2023-01-12 14:43:08 +01:00
youben11
62b417a373 refactor(ci): unify workflows into a single one
Having a single workflow make it easier to have dependencies between
jobs, like release and docker image being dependant of the tests job
2021-12-22 18:22:22 +01:00
youben11
acf91c78a7 fix(ci): disable release worflow run on master with no tag
There were both runs of release for master and the tag push, so we now
match the tag push
2021-12-16 11:43:28 +01:00
youben11
319cc3fd28 fix(python): copy dynamic library into macos wheel 2021-12-16 09:15:25 +01:00
youben11
b812f6f7f2 feat(python): version python package from git tag
automatic detection of version from git tag and update of the python
version file
2021-12-16 09:15:25 +01:00
youben11
a94e05e85b ci: release mac
improve current workflow: more parallelism and factoring of steps with
matrix
2021-12-16 09:15:25 +01:00
youben11
5773310215 feat(ci): release on tag pushed (linux only)
The release workflow should, whenever a tag is pushed,
create a draft release on github (that should be manually
checked by one of us to make the actual release).
The release should contain wheels for python 3.8, 3.9, and 3.10,
as well as a tarball containing the zamacompiler and required
libraries (and installation guide is provided).
The draft release will also have an auto generated release note
that can be modified later.
2021-12-08 17:59:53 +01:00
youben11
4618abcc50 ci: add release workflow
currently only replace one asset from a specific release
2021-12-07 16:14:44 +01:00