Create the python package too

https://github.com/rom1504/taming-transformers/blob/master/.github/workflows/python-publish.yml is a good way to release when a GitHub release is created (put __token__ as user secret, and get a token in pypi for the password)

https://github.com/PrismarineJS/mineflayer/blob/master/.github/workflows/npm-publish.yml if you also have something like this then the release procedure will be to create a commit named “Release x.y.z” containing version update to package.json and setup.py (and maybe a change log) and then everything will be automatic:

• npm publish will publish to npm and create a GitHub release
• that will trigger pypi release which will release to pypi

(For the npm one you also need to put some npm token in secret)

[Carreau]

Ok, I think I fixed it.

Invitation sent.

We can switch to version 2 for the python package I think, since it would be a breaking change. Thanks.

Problem is that the version I published are 2015.x.x, so you either need to delete them (which I’m not even sure would work), or publish a version number greater than 2015.x.x, you can though prepend the version number with 1! to restart the versioning scheme.

Epoch have been made explicitely for this:

However, by specifying an explicit epoch, the sort order can be changed appropriately, as all versions from a later epoch are sorted after versions from an earlier epoch:

2013.10
2014.04
1!1.0
1!1.1
1!2.0

So this will allow you to have lower version numbers seen as more recent.

[Carreau]

Congrats! Don’t forget to remove me as owner of all goes well.

On Thu, Jul 15, 2021, 11:01 Romain Beaumont @.***> wrote:

Closed #1 https://github.com/extremeheat/JSPyBridge/issues/1.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/extremeheat/JSPyBridge/issues/1#event-5024125617, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACR5T57KLT4HLJLWWXWLMDTX2PYBANCNFSM47YAXJDQ .