Fix publishing

[hukkin]

There were two reasons why @KyleKing was unable to publish on PyPI:

• Flit publish is having issues: flit publish fails, 403 Client Error: Username/Password authentication is no longer supported. pypa/flit#686
• The PyPI token is named PYPI_TOKEN in GitHub settings and PYPI_KEY in tests.yml so they wouldn't match.

[KyleKing]

Thanks for publishing v0.2.0 and taking a look!

[KyleKing]

I published mdformat-tables with flit 3.9.0, so there might be an issue with the generated token rather than that flit release:

https://github.com/executablebooks/mdformat-tables/blob/17e79139ed3c288ae8caba84ea834ee2c86c488c/.github/workflows/tests.yml#L90-L98

https://github.com/executablebooks/mdformat-tables/actions/runs/10533763354/job/29190294084
Successfully installed certifi-2024.7.4 charset-normalizer-3.3.2 docutils-0.20.1 flit-3.9.0 flit_core-3.9.0 idna-3.8 requests-2.31.0 tomli-w-1.0.0 urllib3-2.0.7

Would it be worthwhile to try generating a new PyPi token scoped to mdformat-myst before switching to twine?

[hukkin]

Ah ok, perhaps it was then just a matter of setting the proper auth ENV variables for flit publish. I tried to flit publish locally and entered credentials when asked for and got the error I linked to in flit's issue tracker. twine worked fine for me.

I think the token should work fine, but it was referred to by the wrong ENV variable name in tests.yml.