This adds dependency pinning using 'pip compile' from piptools.
This also adds automatic versioning, meaning that the releaser sets the tag and version. This uses the tool 'bump-my-version' to update the version in different places in the package.
The benefit of this is that everything will triggered by the github release (version bump, dependency pinning, upload to pypi), making it very easy to do new releases.
We already have a workflow that gets triggered by the Github release, but there is no version or dependency management. I want to rebase the workflow on the one we did for GEMDAT: https://github.com/GEMDAT-repos/GEMDAT/blob/main/.github/workflows/publish.yaml
This adds dependency pinning using 'pip compile' from piptools.
This also adds automatic versioning, meaning that the releaser sets the tag and version. This uses the tool 'bump-my-version' to update the version in different places in the package.
The benefit of this is that everything will triggered by the github release (version bump, dependency pinning, upload to pypi), making it very easy to do new releases.