Break up actions into one that does linting and tests python build and other that builds and publishes the wheel
Idea is to have the action that does linting and tests that the python package builds correctly run on every push on every branch while the building and publishing the wheels only runs when a change into master occurs.
One thing to think about is the PyPI wheel publishing will ALWAYS fail if the version number was not bumped as we cannot publish a wheel with the same version as wheels previously published to PyPI
This means any PR that has meaningful changes that we want to immediately propagate to PyPI versions of diploshic MUST include a bumped version number
Break up actions into one that does linting and tests python build and other that builds and publishes the wheel
Idea is to have the action that does linting and tests that the python package builds correctly run on every push on every branch while the building and publishing the wheels only runs when a change into master occurs.
One thing to think about is the PyPI wheel publishing will ALWAYS fail if the version number was not bumped as we cannot publish a wheel with the same version as wheels previously published to PyPI
This means any PR that has meaningful changes that we want to immediately propagate to PyPI versions of diploshic MUST include a bumped version number