Sem
@nijanthanvijayakumar @dinjazelena Thanks for the explanation! Do I understand right, that this workflow make a realease to PyPI? If so, which secrets should be provided?
Can we somehow add a step to the release pipeline that publish in PyPI release or pre-release versions?
> Question is only do you want to create automatic release for pre-releases or for production releases I would have better automated prod-release
Sorry, I missed the comment. I will ask @MrPowers
@nijanthanvijayakumar Do I understand you right that all the work is done and the only thing left is adding a trusted publihser to PyPI?
@nijanthanvijayakumar LGTM overall, thanks for the effort and especially for the patience! @dinjazelena Hi! Can I ask you to take a final look on it too?
> @SemyonSinchenko it's been a while since I have looked into Quinn. Wanted to check if we are proceeding with this PR? Thanks! Hello! Im sorry, I was busy for...
@nijanthanvijayakumar Thanks for the contribution!
@kasztp Can you also run a pre-commit with ruff to fix failing code-style check? https://github.com/MrPowers/chispa/actions/runs/11291104694/job/31447515682?pr=141
Sorry, I lost it