Perepare release to PyPi

[elchupanebrej]

🤔 What's changed?

Fixup pyproject.toml to conform with the existing release

⚡️ What's your motivation?

I want to have PyPi released continuously.

🏷️ What kind of change is this?

• 🏦 Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (701105a) 91.17% compared to head (fda5278) 91.17%.
Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #243   +/-   ##
=======================================
  Coverage   91.17%   91.17%           
=======================================
  Files           2        2           
  Lines          34       34           
=======================================
  Hits           31       31           
  Misses          3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mpkorstanje]

We have a release process setup through Github actions. This means that in essence, we only have to set the version number for each implementation and push a git tag (all automated through https://github.com/cucumber/polyglot-release).

So to get the release process working again, I suppose you would have to take your manual instructions and convert them into a Github action.

As a template you could use this commit b00f19a in which I disabled the python release process (#213).

[mpkorstanje]

Heya. @brasmusson has been setting up publishing to PyPi using trusted publishers. This is the ideal solution.

• [Python] Use a trusted publisher to release to Pypi. cucumber-expressions#263
• [Python] Fix release workflow for Python tag-expressions#146

Apologies for changing the desired solution. Things is are changing atypically quick.

[luke-hill]

@elchupanebrej - This probably should have been looked at a while ago. Looking at the 2 linked by @mpkorstanje - it seems as though there is a specific action that is used called pypa/gh-action-pypi-publish@release/v1 - Can we try use that here for standardisation?

[luke-hill]

No longer required