Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove SemVer version validation as it doesnt support version strings…
… such as 1.6.1rc0 (#678) <!-- Thanks for contributing a Pull Request to ArcticDB! Please ensure you have taken a look at: - ArcticDB's Code of Conduct: https://github.com/man-group/ArcticDB/blob/master/CODE_OF_CONDUCT.md - ArcticDB's Contribution Licensing: https://github.com/man-group/ArcticDB/blob/master/docs/mkdocs/docs/technical/contributing.md#contribution-licensing --> #### Reference Issues/PRs <!-- Example: Fixes #1234. See also #3456. Please use keywords (e.g., Fixes) to create link to the issues or pull requests you resolved, so that they will automatically be closed when your pull request is merged. See: https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue --> #### What does this implement/fix? How does it work (high level)? Highlight notable design decisions. #### Any other comments? We could replace this with conda version validation (from the `conda` package) or packaging version validation (from the `packaging` package) but both are a little fiddly. To be honest this has to be approved before having an irreversible effect, so I think human validation is fine here. #### Checklist <details> <summary> Checklist for code changes... </summary> - [x] Have you updated the relevant docstrings and documentation? - [x] Is this contribution tested against [all ArcticDB's features](../docs/mkdocs/docs/technical/contributing.md)? - [x] Do all exceptions introduced raise appropriate [error messages](https://docs.arcticdb.io/error_messages/)? - [x] Are API changes highlighted in the PR description? - [x] Is the PR labelled as enhancement or bug so it appears in autogenerated release notes? </details>
- Loading branch information