Sematic

What's Changed
* [feature] Ability to deploy socket.io micro-service separately.
* [feature] Expose external resources in the dashboard.
* [feature] Slack notification integration for failed resolutions.
* [feature] Support the `debug` query parameter which can be added to any URL to enforce the front-end application to emit logs.
* [improvement] Minor dependency and CI improvement.
* [improvement] Minor development documentation improvements.
* [bugfix] Fix a bug in the dashboard which prevents successful resolution of status update.

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.22.2...v0.23.0

Compatibility
Sematic servers on this version can support pip packages back to version v0.21.1

What's Changed
- [feature] Add the ability to cache the output of a function and avoid its re-execution in the future
- [feature] Add the ability to disable Sematic log ingestion for remote runs
- [feature] Expose cloned run information in the dashboard
- [improvement] Minor logging improvements
- [improvement] Support configuring plugins from the CLI
- [improvement] Add support for Bazel 6.0.0
- [improvement] Add a link in output panel pointing to logs panel in case of error
- [improvement] Improve robustness of data persistence
- [improvement] Minor Helm documentation improvements
- [improvement] Make the header sticky on the run details page
- [improvement] Minor dashboard experience improvement
- [improvement] Internal API endpoints expansion
- [improvement] Support for non-deterministic cached builds in Bazel
- [bugfix] Support override of settings even when no settings file exists
- [bugfix] Minor cross version client support fixes
- [bugfix] Make _getitem importable on graph cloning

Compatibility
Sematic servers on this version can support pip packages back to version v0.21.1

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.22.1...v0.22.2

What's Changed
- [feature] Hide some "utility" autogenerated runs in the UI (ex: `_getitem`)
- [improvement] Added functionality to some server APIs
- [bugfix] To the script to allow auto-upgrading settings files. IMPORTANT: Users should run `sematic migrate` upon install

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.22.0...v0.22.1

Migration
⚠️ Users should run this command after installation in order to migrate their settings files:
bash
$ sematic migrate


Compatibility
The new 0.22.1 Server supports communicating with Clients with version 0.21.1 or later, but it introduces new features which are only available for Clients versions 0.22.0 or later.

What's Changed
- [feature] Expose in the dashboard when a run is cloned from another
- [feature] Allow specifying multiple e-mail domains that can authenticate to Sematic
- [feature] Deep linking for highlighting nested runs in the dashboard
- [feature] Deep linking for tabs in the dashboard
- [feature] Support clicking artifacts in the DAG view to get to their display page
- [feature] Allow configuration for expanded shared memory on cloud workers
- [feature] BREAKING CHANGE: Significant changes to our helm chart. Read our [deployment docs](https://docs.sematic.dev/diving-deeper/deploy) for more information.
- [improvement] Improvements to logging UI performance
- [improvement] Give an error message if there are futures that are not used for a function's final output
- [improvement] Avoid warning about SQLite version when SQLite is not in use
- [improvement] User-facing documentation revamp
- [bugfix] Add sematic.testing to python wheel
- [bugfix] Fix a bug with deserializing Tuple objects
- [bugfix] Propagate tags and properties to cloned runs
- [bugfix] Improve the behavior of the logging UI in case of errors
- [bugfix] Better display of Union types in the dashboard
- [bugfix] Add a missing requirement for one of the example pipelines
- [bugfix] Prevent the dashboard from spamming the backend with requests
- [bugfix] Fix corrupted settings files from 0.21.1

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.21.1...v0.22.0

Compatibility
The new 0.22.0 Server supports communicating with Clients with version 0.21.1 or later, but it introduces new features which are only available for Clients with the new 0.22.0 version.

What's Changed
* [bugfix] Add back feature allowing configuration of custom API URL to be used by workers

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.21.0...v0.21.1

What's Changed
* [feature] Add CLI for reading/following logs for a run
* [feature] Enable configuration for the Kubernetes service account the workers will use
* [feature] Enable getting the id of the current run and root run from inside a Sematic func
* [feature] Add custom display for Enum objects
* [improvement] Settings file split between user settings `settings.yaml` and server settings `server.yaml`
* [improvement] Make the run links in notes more obvious
* [improvement] Fail early if attempting to retry an execution older than the server supports.
* [bugfix] Fix a bug deserializing `Union` values. Note that once you are using this release, if you try to "rerun from here" using a pipeline that has `Union` values in it that were produced prior to this version of Sematic, the rerun will likely fail with a serialization issue.
* [bugfix] BREAKING CHANGE: The examples' `README` files have been renamed to `README.md` in order for them to correctly render as MarkDown files. This change is required by the Bazel `example_pipeline` target as well
* [bugfix] Missing broadcasts upon server-side run save
* [bugfix] Cache version check
* [bugfix] Fix a bug with loading logs with in-progress runs when you have reached the end
* [bugfix] Fix a bug with displaying matplotlib figures in cloud deployments

+ a variety of "behind-the-scenes" changes & refactors

New Contributors
* KatkaG made their first contribution in https://github.com/sematic-ai/sematic/pull/324

Thank you KatkaG for your contribution!

**Full Changelog**: https://github.com/sematic-ai/sematic/compare/v0.20.1...v0.21.0