Dmitriy
Dmitriy
@xomiamoore No, I made a hack: I added empty jobs for python3.6 and python3.7 to workflow, see https://github.com/camunda-community-hub/pyzeebe/pull/398/commits/e9bf785eeace61712b172ab78517bedcdad74a73. But we should remove these jobs from branch ruleset, because of EOL...
@xomiamoore @JonatanMartens Hi! Can you add `PYPI_TOKEN` (https://github.com/camunda-community-hub/pyzeebe/blob/master/.github/workflows/publish.yml#L26) to environment variables? As I see on pypi, @JonatanMartens is owner of https://pypi.org/project/pyzeebe/. I would like to create new prerelease https://github.com/camunda-community-hub/pyzeebe/releases
@xomiamoore yes, [dima_st_bk](https://readthedocs.org/profiles/dima_st_bk/)
@JonatanMartens hi. Can you send invite again? I missed the link and it has expired.
@xomiamoore Hi. Yes.
@JonatanMartens Hi. Can you send invite to RTD again? I missed the link and it has expired.
It seems that legacy checks are presented in "[require status checks to pass](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging)" ruleset settings.
@xomiamoore fixed. But currently, pyzeebe doesn't declare support for python 3.12. And I planned to fix this test in the future.
@xomiamoore test wasn't a problem. I still can’t merge it 
https://github.com/camunda-community-hub/pyzeebe/pull/383