[CI] Build/publish wheels #4
Conversation
|
Converted to Draft since after doing a test publish (on my fork) the TestPyPI page includes the whole README, a lot of which assumes you've cloned the repo. So we either need a separate README or to massage the existing README to work in multiple contexts. |
TraitGen is now a separate project, so the relative path link was broken. Signed-off-by: David Feltell <david.feltell@foundry.com>
In particular, this is useful in preparation for PyPI publishing in #2, where (parts of) the README will be published independently of the repo. Signed-off-by: David Feltell <david.feltell@foundry.com>
feltech
force-pushed
the
work/2-publishPyPI
branch
5 times, most recently
from
38b36f9 to
aa06754
Compare
Updated. I screwed up for the first couple of test releasees and didn't add a TestPyPI release: https://test.pypi.org/project/openassetio-traitgen/ |
elliotcmorris
left a comment
elliotcmorris
left a comment
There was a problem hiding this comment.
Looks fab. One super minor note.
Closes #2. This will allow dependent projects such as https://github.com/OpenAssetIO/OpenAssetIO-MediaCreation to automate its use as part of their build pipeline. Build wheels on PR or and merge to `main`. Publish wheels built on `main` for release. Waiting for wheels to be built before publishing, if not already (see `concurrency.group` in the `.yml` files). Signed-off-by: David Feltell <david.feltell@foundry.com>
feltech
force-pushed
the
work/2-publishPyPI
branch
from
fd8f428 to
9d74f62
Compare
2 participants
Closes #2. This will allow dependent projects such as https://github.com/OpenAssetIO/OpenAssetIO-MediaCreation to automate its use as part of their build pipeline.
Build wheels on PR or and merge to
main. Publish wheels built onmainfor release. Waiting for wheels to be built before publishing, if not already (seeconcurrency.groupin the.ymlfiles).