Sematic

What's Changed
* Add Sematic version cli command
* Fix cancel button upon completion
* Bump minimum client version to 0.17.0
* Fix GitInfo for custom Bazel workspaces

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.17.0...v0.17.1

What's Changed
* Function Retry on failure
* Expose pipeline git commit info in the UI
* Cancel resolution support

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.16.0...v0.17.0

What's Changed

* Support enums in Sematic function annotations
* Allow specifying Kubernetes tolerations for cloud jobs
* Redesign log view UI
**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.15.1...v0.16.0

What's Changed

* Ensure log ingestion happens when using bazel cloud jobs and `dev=False`
* Avoid spamming the server with requests for logs for incomplete runs
without logs

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.15.0...v0.15.1

What's Changed

* Display logs for cloud jobs in the UI. **Note**: This feature will require your server to have the ability to list objects in the S3 bucket you're using for Sematic storage.
* Ensure the push of docker images by bazel works with docker credential helpers
**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.14.0...v0.15.0

What's Changed
In prior versions, anyone who needed to submit a pipeline execution had to get set up to access the Kubernetes cluster where the jobs would run. As of this release, users only need to get set up to access a Sematic server, and the server will handle all communication with Kubernetes. This improves user experience as well as security. It does mean that anyone running cloud execution may need to change their deployment so that the server can access Kubernetes. We've updated [the deployment docs](https://docs.sematic.dev/diving-deeper/deploy) with instructions and created a Helm chart to ease deployment. As a summary of this release:

* BREAKING CHANGE: For cloud execution, users submitting pipelines for execution no longer need Kubernetes access. Users who have deployed the Sematic server using docker will need to either (a) switch to deploying the server on Kubernetes or (b) use their Sematic deployment only for metadata tracking instead of metadata tracking + cloud execution.
* Remove job environment variables from resolution API response
* Lower the probability of evictions of resolution jobs and improve handling of that situation
**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.13.0...v0.14.0