Allow publishing to pypi when tags are pushed

[GiacomoPope]

So the goal of this PR is to get the project ready so that new tags push the project to pypi too.

Maybe I need to do more for this to work, and the CI seems to be failing for something adjacent?

Edit: failure is because https://coveralls.io is down right now.

[tomato42]

not familiar with the github actions workflows to publish to pypi so can't say one way or the other if it's correct; "passes sniff test" is the best I can do 🙂

[tomato42]

shouldn't this be "1.0.0" ?

we have https://github.com/GiacomoPope/kyber-py/releases/tag/v1.0 ...

[GiacomoPope]

Yeah I agree

[webknjaz]

Perhaps, something newer since the repo advanced since?

Suggested change

	version = "0.1.0"
	version = "1.0.1.dev0"

[GiacomoPope]

what's the meaning of the dev0 part? I would be ok with 1.0.1

[tomato42]

it's so that if somebody installs the package from a git checkout, and then updates packages with pip, they get the actual released 1.0.1 version

[webknjaz]

Yeah, 1.0.1.dev0 < 1.0.1 during dependency resolution. It's one of the possible pre-releases. See PEP 440 for more details.

[webknjaz]

Some projects advance Git to .dev0 right after cutting a release and then bump to a stable version before making the next one.

[webknjaz]

One blocker + a thing to consider.

[GiacomoPope]

Thanks for the additional suggestions, I must have misclicked when committing your suggestions. If you agree now, I will push the tag 1.0.1.dev0 and if this passes and uploads to pypi then I will do a second tag for 1.0.1

[webknjaz]

Sounds good. Don't forget to commit the version bump before doing the second tag.

[GiacomoPope]

@webknjaz thanks for all your help! Looks like it worked!

https://pypi.org/project/kyber-py/