chore: run tests on linux, macos and windows and release builds on ta…

[AntoineRR]

Description

This PR fixes #310

This is a proposal for a new CI/CD pipeline:

• On push and pull requests -> Run rust CI + Tests on Linux / Windows / Macos for python 3.7, 3.8, 3.9, 3.10, 3.11
• On tag creation -> Build for all OS and Python versions and upload to pypi

It seems like the tests do not pass on windows for now, adding this CI could be a good first step to fix them.

[netlify]

✅ Deploy Preview for robyn canceled.

Name	Link
🔨 Latest commit	ec228cf
🔍 Latest deploy log	https://app.netlify.com/sites/robyn/deploys/63d053cf0e4acb00080ed4ab

[sansyrox]

niceee.

[AntoineRR]

I didn't know that was a thing until I worked on this PR 😄

[sansyrox]

nicee..

[sansyrox]

It seems like the tests do not pass on windows for now

I might have a hunch why this is happening. The sockets package is not super compatible with windows. Read the first line here(https://docs.python.org/3/library/socket.html)

Just one question , how is the proposal different from our current way? Don't we still build a package on every PR and push to main?

And release on tags?

[AntoineRR]

Ok thanks, that's a first step for investigating the comptibility with Windows.

There is a difference, as with this PR there are a lot less jobs running on push and PRs (see the pipeline of this PR for reference). Also, previously we built a release package on every push and PRs, but didn't do anything with it. The only time when the builds were used was when a tag was released that would trigger the "Release" job for an upload to Pypi.

In summary:

Previous pipeline:

• Push / PR => Run Rust CI + Run tests on Linux with each Python version + Build a Release package for each OS and each Python version
• Tag creation => All of the above + Publish all Release to Pypi

This pipeline:

• Push / PR => Run Rust CI + Run tests on all OS with each Python version
• Tag creation => All of the above + Build a Release package for each OS and each Python version + Publish all Release to Pypi

I didn't test the tag creation pipeline, but kept the same jobs as before so it should work fine

[sansyrox]

@AntoineRR , in this PR , are we depending on the tests to pass to build the packages?

[AntoineRR]

@sansyrox no, the test and release workflow are independant of each other

[sansyrox]

This looks good! Now we have more information about windows builds!