Automatically deploy new tagged versions to PyPI

[tschneidereit]

We should switch to automatically deploying the Python extension whenever we bump the Wasmtime version number, based on the whl packages our CI builds.

/cc @yurydelendik

[luizirber]

Hi, I recently opened two PRs (#627 and #648) that touch the Python wheel generation, and since now the generated wheels have the right names (and version) I can look into using https://github.com/pypa/gh-action-pypi-publish to publish the wheels to PyPI.

Should I make a new PR?

I obviously don't have permissions to manage the repo secret here in GitHub nor create the PyPI token for upload, so someone with access to those would need to fill it in.

[alexcrichton]

That'd be awesome if you could help us tackle this @luizirber, thanks!

If you want to test out on a local copy of the repo and let us know what secrets to configure, we can do that and then merge a PR!

[OrangeTux]

@luizirber Are you still working on this? Is there a way I can help?

[luizirber]

@OrangeTux feel free to take this one, I didn't do anything other than ask =]

[OrangeTux]

@luizirber Cool, I'll take a look at the issue than.

[OrangeTux]

I'm not sure if something is wrong with the workflow. The workflow for 0.9.0 release has failed, although there are some files uploaded to pypi

[alexcrichton]

@OrangeTux mind helping us to fix this? Some debugging looks like our usage of packages_dir isn't supported by the v1.0.0a0 tag, but it is supported on master. I think we may have a duplicate directory called dist which caused the build to not fail, but there was probably some stray files in dist which cause the upload to fail. I suspect that if we fixed the directory stuff the publication would finish?

We can probably pin to a specific revision of the action on the master branch and get this working?

[OrangeTux]

Sure, I am happy to help. Although it probably needs to wait till it is weekend.

[OrangeTux]

To me it seems that we've 2 different issues:

1. The first issue is the one you described: the master version of the gh-action-pypi-publish@v1.0.0a0 is not supported.

2. The second issue is that job for uploading the Python wheels to Pypi has run at least twice for v0.9.0. The first time was at the build of commit 5427a8e.
   You can see that the job Publish Python wheels on Pypi has ran. It uploaded 9 wheel files to Pypi before the gh-action-pypi-publish encountered an unknown file format and failed. It probably encountered this file because of issue 1: the action is not respecting the packages_dir.
   Than this job Publish Python wheels on Pypi is ran again for commit 632e525. Now the job fails because you cannot republish packages to Pypi with the same name.
   The question is why this job has run twice for the same tag? Did someone retagged v0.9.0?

[OrangeTux]

I opened an issue and asked if the author can create a new release.

[alexcrichton]

According to this documentation it looks like we don't have to necessarily wait for a release, we can pin to a specific revision? We can likely pin to whatever master is right now and update it to a release next time that happens

As for the double-tag I'm not sure, but it's something we can keep an eye out for in the future!