Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM except that I would publish to TestPyPi first. See suggestion.
| .github/workflows/release-tasks.yml | ||
|---|---|---|
| 89–92 | I suggest to first try publishing to https://test.pypi.org/ and only if that works, use the official pypi. | |
Does lit have any test suite? In that case, I suggest the tests should be executed before uploading.
| llvm/utils/lit/lit/__init__.py | ||
|---|---|---|
| 6 | Not sure I love this change. If a user builds a lit version locally, it should still include the dev suffix. Maybe we could substitute this or something when building the release? | |
| .github/workflows/release-tasks.yml | ||
|---|---|---|
| 81 | This should do the trick. I missed entering the directory in my first suggestion. | |
| llvm/utils/lit/lit/__init__.py | ||
|---|---|---|
| 6 | This was not meant to be part of the patch, I will remove it. There is code in the GitHub action that strips out the 'dev' before uploading. | |
Looks much better now. Thank you for applying my suggestions @tstellar ! As usual I hope the github action runs and is valid YAML. There's just one more thing where I need confirmation on: Have you tried running the Upload lit TestPyPI step? I've done releases to pypi and test.pypi in the recent past and I'm nearly 100% sure that you need a second API token for this. Here you're using LLVM_LIT_PYPI_API_TOKEN both, for the Upload lit TestPyPI step as well as the Upload lit.
| .github/workflows/release-tasks.yml | ||
|---|---|---|
| 94 | ||
| 97 | I'm pretty sure you need need a different token for this than for the final upload to pypi. Try to log in to test.pypi.org and see for yourself. | |
| 100 | ||
This should do the trick. I missed entering the directory in my first suggestion.