Travis CI, with the move to travis-ci.com, now requires to request OSS credits for open source projects, which might be a lot of burden for a project like this. I would instead recommend moving to github actions, which is completely free for open source projects.
The initial issue also mentions "I don't know if this is also affecting the release new versions or if tags need to be created manually.", but I didnt find any reference of automated deployment of versions based on the tags created. Is there something I am missing?
Summary
Move from travis CI to Github Actions.
Why?
Travis CI, with the move to travis-ci.com, now requires to request OSS credits for open source projects, which might be a lot of burden for a project like this. I would instead recommend moving to github actions, which is completely free for open source projects.
The initial issue also mentions "I don't know if this is also affecting the release new versions or if tags need to be created manually.", but I didnt find any reference of automated deployment of versions based on the tags created. Is there something I am missing?
Closes #25