Replacing releases breaks downstream package management
17.0.0 released a second time with modifications, breaking downstream package management that verifies integrity of releases (shasums) -
please increment versions regardless of the time between releases to avoid headaches downstream.
17.0.0 has not been released yet. Do you mean the release draft?
https://github.com/Keeper-Security/Commander/releases/tag/v17.0.0 tagged pre-
I see the release has now been deleted, breaking package management downstream again.
Is it not safe to assume pre-releases will not be replaced/deleted after being published? I can understand releases being removed due to security concerns or packaging issues, but it seems as though things are changing without such reasons?
We currently have some issues releasing the Commander to PyPI. Once those issues are resolved the binaries will be published to Github.