PyPI - zenml-nightly - Versions diffs - 0.71.0.dev20250105__py3-none-any.whl → 0.71.0.dev20250107__py3-none-any.whl - Mend

zenml-nightly 0.71.0.dev20250105py3-none-any.whl → 0.71.0.dev20250107py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (16) hide show

zenml/VERSION +1 -1
zenml/zen_server/auth.py +21 -2
zenml/zen_server/routers/auth_endpoints.py +2 -1
zenml/zen_stores/rest_zen_store.py +11 -1
{zenml_nightly-0.71.0.dev20250105.dist-info → zenml_nightly-0.71.0.dev20250107.dist-info}/METADATA +2 -2
{zenml_nightly-0.71.0.dev20250105.dist-info → zenml_nightly-0.71.0.dev20250107.dist-info}/RECORD +9 -16
{zenml_nightly-0.71.0.dev20250105.dist-info → zenml_nightly-0.71.0.dev20250107.dist-info}/WHEEL +1 -1
CLA.md +0 -110
CODE-OF-CONDUCT.md +0 -132
CONTRIBUTING.md +0 -260
README.md +0 -342
RELEASE_NOTES.md +0 -5722
ROADMAP.md +0 -5
SECURITY.md +0 -15
{zenml_nightly-0.71.0.dev20250105.dist-info → zenml_nightly-0.71.0.dev20250107.dist-info}/LICENSE +0 -0
{zenml_nightly-0.71.0.dev20250105.dist-info → zenml_nightly-0.71.0.dev20250107.dist-info}/entry_points.txt +0 -0

CONTRIBUTING.md DELETED Viewed

@@ -1,260 +0,0 @@
-# 🧑‍💻 Contributing to ZenML
-A big welcome and thank you for considering contributing to ZenML! It’s people
-like you that make it a reality for users
-in our community.
-Reading and following these guidelines will help us make the contribution
-process easy and effective for everyone
-involved. It also communicates that you agree to respect the developers' time
-management and develop these open-source projects. In return, we will reciprocate that respect by reading your
-issue, assessing changes, and helping
-you finalize your pull requests.
-## ⚡️ Quicklinks
-- [🧑‍💻 Contributing to ZenML](#-contributing-to-zenml)
-  - [⚡️ Quicklinks](#-quicklinks)
-  - [🧑‍⚖️ Code of Conduct](#-code-of-conduct)
-  - [🛫 Getting Started](#-getting-started)
-    - [⁉️ Issues](#-issues)
-    - [🏷 Pull Requests: When to make one](#-pull-requests-when-to-make-one)
-    - [💯 Pull Requests: Workflow to Contribute](#-pull-requests-workflow-to-contribute)
-    - [🧱 Pull Requests: Rebase on develop](#-pull-requests-rebase-your-branch-on-develop)
-    - [🧐 Linting, formatting, and tests](#-linting-formatting-and-tests)
-    - [🚨 Reporting a Vulnerability](#-reporting-a-vulnerability)
-  - [Coding Conventions](#coding-conventions)
-  - [👷 Creating a new Integration](#-creating-a-new-integration)
-  - [🆘 Getting Help](#-getting-help)
-## 🧑‍⚖️ Code of Conduct
-We take our open-source community seriously and hold ourselves and other
-contributors to high standards of communication.
-By participating and contributing to this project, you agree to uphold
-our [Code of Conduct](https://github.com/zenml-io/zenml/blob/master/CODE-OF-CONDUCT.md)
-.
-## 🛫 Getting Started
-Contributions are made to this repo via Issues and Pull Requests (PRs). A few
-general guidelines that cover both:
-- To report security vulnerabilities, please get in touch
-  at [support@zenml.io](mailto:support@zenml.io), monitored by
-  our security team.
-- Search for existing Issues and PRs before creating your own.
-- We work hard to make sure issues are handled on time, but it could take a
-  while to investigate the root cause depending on the impact.
-A friendly ping in the comment thread to the submitter or a contributor can help
-draw attention if your issue is blocking.
-### Good First Issues for New Contributors
-The best way to start is to check the
-[`good-first-issue`](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22)
-label on the issue board. The core team creates these issues as necessary
-smaller tasks that you can work on to get deeper into ZenML internals. These
-should generally require relatively simple changes, probably affecting just one
-or two files which we think are ideal for people new to ZenML.
-The next step after that would be to look at the
-[`good-second-issue`](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+second+issue%22)
-label on the issue board. These are a bit more complex, might involve more
-files, but should still be well-defined and achievable to people relatively new
-to ZenML.
-### ⁉️ Issues
-Issues should be used to report problems with the library, request a new
-feature, or to discuss potential changes before
-a PR is created. When you create a new Issue, a template will be loaded that
-will guide you through collecting and
-providing the information we need to investigate.
-If you find an Issue that addresses your problem, please add your own
-reproduction information to the
-existing issue rather than creating a new one. Adding
-a [reaction](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
-can also help by
-indicating to our maintainers that a particular issue is affecting more than
-just the reporter.
-### 🏷 Pull Requests: When to make one
-Pull Requests (PRs) to ZenML are always welcome and can be a quick way to get your fix or
-improvement slated for the next release. In
-general, PRs should:
-- Only fix/add the functionality in question **OR** address widespread
-  whitespace/style issues, not both.
-- Add unit or integration tests for fixed or changed functionality (if a test
-  suite already exists).
-- Address a single concern in the least number of changed lines as possible.
-- Include documentation in the repo or in your Pull Request.
-- Be accompanied by a filled-out Pull Request template (loaded automatically when
-  a PR is created).
-For changes that address core functionality or would require breaking changes (e.g. a major release), it's best to open
-an Issue to discuss your proposal first. This is not required but can save time
-creating and reviewing changes.
-### 💯 Pull Requests: Workflow to Contribute
-<p class="callout warning">Please note that development in ZenML happens off of the <b>develop</b> branch, <b>not main</b>,
-which is the default branch on GitHub. Therefore, please pay particular attention to step 5 and step 9 below. </p>
-In general, we follow
-the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr)
-1. Review and sign
-   the [Contributor License Agreement](https://cla-assistant.io/zenml-io/zenml) (
-   CLA).
-2. Fork the repository to your own Github account.
-3. Clone the project to your machine.
-4. Checkout the **develop** branch <- `git checkout develop`.
-5. Create a branch (again, off of the develop branch) locally with a succinct but descriptive name.
-6. Commit changes to the branch
-7. Follow the `Linting, formatting, and tests` guide to make sure your code adheres to the ZenML coding style (see below).
-8. Push changes to your fork.
-9. Open a PR in our repository (to the `develop` branch, **NOT** `main`) and
-   follow the PR template so that we can efficiently review the changes.
-### 🧱 Pull Requests: Rebase Your Branch on Develop
-1. When making pull requests to ZenML, you should always make your changes on a branch that is based on `develop`. You can create a new branch based on `develop` by running the following command:
-   ```
-   git checkout -b <new-branch-name> develop
-   ```
-2. Fetch the latest changes from the remote `develop` branch:
-   ```
-   git fetch origin develop
-   ```
-3. Switch to your branch:
-   ```
-   git checkout <your-branch-name>
-   ```
-4. Rebase your branch on `develop`:
-   ```
-   git rebase origin/develop
-   ```
-   This will apply your branch's changes on top of the latest changes in `develop`, one commit at a time.
-5. Resolve any conflicts that may arise during the rebase. Git will notify you if there are any conflicts that need to be resolved. Use a text editor to manually resolve the conflicts in the affected files.
-6. After resolving the conflicts, stage the changes:
-   ```
-   git add .
-   ```
-7. Continue the rebase for all of your commits and go to 5) if there are conflicts.
-   ```
-   git rebase --continue
-   ```
-8. Push the rebased branch to your remote repository:
-   ```
-   git push origin --force <your-branch-name>
-   ```
-9. Open a pull request targeting the `develop` branch. The changes from your rebased branch will now be based on the latest `develop` branch.
-### 🧐 Linting, formatting, and tests
-To install ZenML from your local checked out files including all core dev-dependencies, run:
-```
-pip install -e ".[server,dev]"
-```
-Optionally, you might want to run the following commands to ensure you have all
-integrations for `mypy` checks:
-```
-zenml integration install -y -i feast
-pip install click~=8.0.3
-mypy --install-types
-```
-Warning: This might take a while for both (~ 15 minutes each, depending on your machine), however if you have
-time, please run it as it will make the
-next commands error-free. Note that the `zenml integration install` command
-might also fail on account of dependency conflicts so you can just install the
-specific integration you're working on and manually run the mypy command for the
-files you've been working on.
-You can now run the following scripts to automatically format your
-code and to check whether the code formatting, linting, docstrings, and
-spelling is in order:
-```
-bash scripts/format.sh
-bash scripts/run-ci-checks.sh
-```
-If you're on Windows you might have to run the formatting script as `bash
-scripts/format.sh --no-yamlfix` and run the yamlfix command separately as
-`yamlfix .github -v`.
-Tests can be run as follows:
-```
-bash scripts/test-coverage-xml.sh
-```
-Please note that it is good practice to run the above commands before submitting
-any Pull Request: The CI GitHub Action
-will run it anyway, so you might as well catch the errors locally!
-### 🚨 Reporting a Vulnerability
-Please refer to [our security / reporting instructions](./SECURITY.md) for
-details on reporting vulnerabilities.
-## Coding Conventions
-The code within the repository is structured in the following way -
-the most relevant places for contributors are highlighted with a `<-` arrow:
-```
-├── .github           -- Definition of the GH action workflows
-├── docker            -- Dockerfiles used to build ZenML docker images
-├── docs              <- The ZenML docs, CLI docs and API docs live here
-│   ├── book          <- In case you make user facing changes, update docs here
-│   └── mkdocs        -- Some configurations for the API/CLI docs
-├── examples          <- When adding an integration, add an example here
-├── scripts           -- Scripts used by Github Actions or for local linting/testing
-├── src/zenml         <- The heart of ZenML
-│   ├── <stack_component>   <- Each stack component has its own directory
-│   ├── cli                 <- Change and improve the CLI here
-│   ├── config              -- The ZenML config methods live here
-│   ├── integrations        <- Add new integrations here
-│   ├── io                  -- File operation implementations
-│   ├── materializers       <- Materializers responsible for reading/writing artifacts
-│   ├── pipelines           <- The base pipeline and its decorator
-│   ├── services            -- Code responsible for managing services
-│   ├── stack               <- Stack, Stack Components and the flavor registry
-│   ├── steps               <- Steps and their decorators are defined here
-│   ├── utils               <- Collection on useful utils
-│   ├── zen_server          -- Code for running the Zen Server
-│   └── zen_stores          -- Code for storing stacks in multiple settings
-└── test              <- Don't forget to write unit tests for your code
-```
-## 👷 Creating a new Integration
-In case you want to create an entirely new integration that you would like to
-see supported by ZenML there are a few steps that you should follow:
-1. Create the actual integration. Check out the
-[Integrations README](src/zenml/integrations/README.md)
-for detailed step-by-step instructions.
-2. Create an example of how to use the integration. Check out the
-[Examples README](examples/README.md)
-to find out what to do.
-3. All integrations deserve to be documented. Make sure to pay a visit to the
-[Component Guide](https://docs.zenml.io/stack-components/component-guide)
-in the docs and add your implementations.
-## 🆘 Getting Help
-Join us in the [ZenML Slack Community](https://zenml.io/slack-invite/) to
-interact directly with the core team and community at large. This is a good
-place to ideate, discuss concepts or ask for help.

README.md DELETED Viewed

@@ -1,342 +0,0 @@
-<div align="center">
-  <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=0fcbab94-8fbe-4a38-93e8-c2348450a42e" />
-  <h1 align="center">Connecting data science teams seamlessly to cloud infrastructure.
-</h1>
-</div>
-<!-- PROJECT SHIELDS -->
-<!--
-*** I'm using markdown "reference style" links for readability.
-*** Reference links are enclosed in brackets [ ] instead of parentheses ( ).
-*** See the bottom of this document for the declaration of the reference variables
-*** for contributors-url, forks-url, etc. This is an optional, concise syntax you may use.
-*** https://www.markdownguide.org/basic-syntax/#reference-style-links
--->
-<div align="center">
-  <!-- PROJECT LOGO -->
-  <br />
-    <a href="https://zenml.io">
-      <img alt="ZenML Logo" src="docs/book/.gitbook/assets/header.png" alt="ZenML Logo">
-    </a>
-  <br />
-  [![PyPi][pypi-shield]][pypi-url]
-  [![PyPi][pypiversion-shield]][pypi-url]
-  [![PyPi][downloads-shield]][downloads-url]
-  [![Contributors][contributors-shield]][contributors-url]
-  [![License][license-shield]][license-url]
-  <!-- [![Build][build-shield]][build-url] -->
-  <!-- [![CodeCov][codecov-shield]][codecov-url] -->
-</div>
-<!-- MARKDOWN LINKS & IMAGES -->
-<!-- https://www.markdownguide.org/basic-syntax/#reference-style-links -->
-[pypi-shield]: https://img.shields.io/pypi/pyversions/zenml?color=281158
-[pypi-url]: https://pypi.org/project/zenml/
-[pypiversion-shield]: https://img.shields.io/pypi/v/zenml?color=361776
-[downloads-shield]: https://img.shields.io/pypi/dm/zenml?color=431D93
-[downloads-url]: https://pypi.org/project/zenml/
-[codecov-shield]: https://img.shields.io/codecov/c/gh/zenml-io/zenml?color=7A3EF4
-[codecov-url]: https://codecov.io/gh/zenml-io/zenml
-[contributors-shield]: https://img.shields.io/github/contributors/zenml-io/zenml?color=7A3EF4
-[contributors-url]: https://github.com/zenml-io/zenml/graphs/contributors
-[license-shield]: https://img.shields.io/github/license/zenml-io/zenml?color=9565F6
-[license-url]: https://github.com/zenml-io/zenml/blob/main/LICENSE
-[linkedin-shield]: https://img.shields.io/badge/-LinkedIn-black.svg?style=for-the-badge&logo=linkedin&colorB=555
-[linkedin-url]: https://www.linkedin.com/company/zenml/
-[twitter-shield]: https://img.shields.io/twitter/follow/zenml_io?style=for-the-badge
-[twitter-url]: https://twitter.com/zenml_io
-[slack-shield]: https://img.shields.io/badge/-Slack-black.svg?style=for-the-badge&logo=linkedin&colorB=555
-[slack-url]: https://zenml.io/slack-invite
-[build-shield]: https://img.shields.io/github/workflow/status/zenml-io/zenml/Build,%20Lint,%20Unit%20&%20Integration%20Test/develop?logo=github&style=for-the-badge
-[build-url]: https://github.com/zenml-io/zenml/actions/workflows/ci.yml
----
-## ⭐️ Show Your Support
-If you find ZenML helpful or interesting, please consider giving us a star on GitHub. Your support helps promote the project and lets others know that it's worth checking out.
-Thank you for your support! 🌟
-[![Star this project](https://img.shields.io/github/stars/zenml-io/zenml?style=social)](https://github.com/zenml-io/zenml/stargazers)
-## 🤸 Quickstart
-[![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/zenml-io/zenml/blob/main/examples/quickstart/quickstart.ipynb)
-[Install ZenML](https://docs.zenml.io/getting-started/installation) via [PyPI](https://pypi.org/project/zenml/). Python 3.9 - 3.12 is required:
-```bash
-pip install "zenml[server]" notebook
-```
-Take a tour with the guided quickstart by running:
-```bash
-zenml go
-```
-## 🪄 Simple, integrated, End-to-end MLOps
-### Create machine learning pipelines with minimal code changes
-ZenML is a MLOps framework intended for data scientists or ML engineers looking to standardize machine learning practices. Just add `@step` and `@pipeline` to your existing Python functions to get going. Here is a toy example:
-```python
-from zenml import pipeline, step
-@step  # Just add this decorator
-def load_data() -> dict:
-    training_data = [[1, 2], [3, 4], [5, 6]]
-    labels = [0, 1, 0]
-    return {'features': training_data, 'labels': labels}
-@step
-def train_model(data: dict) -> None:
-    total_features = sum(map(sum, data['features']))
-    total_labels = sum(data['labels'])
-    print(f"Trained model using {len(data['features'])} data points. "
-          f"Feature sum is {total_features}, label sum is {total_labels}")
-@pipeline  # This function combines steps together
-def simple_ml_pipeline():
-    dataset = load_data()
-    train_model(dataset)
-if __name__ == "__main__":
-    run = simple_ml_pipeline()  # call this to run the pipeline
-```
-![Running a ZenML pipeline](/docs/book/.gitbook/assets/readme_basic_pipeline.gif)
-### Easily provision an MLOps stack or reuse your existing infrastructure
-The framework is a gentle entry point for practitioners to build complex ML pipelines with little knowledge required of the underlying infrastructure complexity. ZenML pipelines can be run on AWS, GCP, Azure, Airflow, Kubeflow and even on Kubernetes without having to change any code or know underlying internals.
-ZenML provides different features to aid people to get started quickly on a remote setting as well. If you want to deploy a remote stack from scratch on your selected cloud provider, you can use the 1-click deployment feature either through the dashboard:
-![Running a ZenML pipeline](/docs/book/.gitbook/assets/one-click-deployment.gif)
-Or, through our CLI command:
-```bash
-zenml stack deploy --provider aws
-```
-Alternatively, if the necessary pieces of infrastructure are already deployed, you can register a cloud stack seamlessly through the stack wizard:
-```bash
-zenml stack register <STACK_NAME> --provider aws
-```
-Read more about [ZenML stacks](https://docs.zenml.io/user-guide/production-guide/understand-stacks).
-### Run workloads easily on your production infrastructure
-Once you have your MLOps stack configured, you can easily run workloads on it:
-```bash
-zenml stack set <STACK_NAME>
-python run.py
-```
-```python
-from zenml.config import ResourceSettings, DockerSettings
-@step(
-  settings={
-    "resources": ResourceSettings(memory="16GB", gpu_count="1", cpu_count="8"),
-    "docker": DockerSettings(parent_image="pytorch/pytorch:1.12.1-cuda11.3-cudnn8-runtime")
-  }
-)
-def training(...):
-	...
-```
-![Workloads with ZenML](/docs/book/.gitbook/assets/readme_compute.gif)
-### Track models, pipeline, and artifacts
-Create a complete lineage of who, where, and what data and models are produced.
-You’ll be able to find out who produced which model, at what time, with which data, and on which version of the code. This guarantees full reproducibility and auditability.
-```python
-from zenml import Model
-@step(model=Model(name="classification"))
-def trainer(training_df: pd.DataFrame) -> Annotated["model", torch.nn.Module]:
-	...
-```
-![Exploring ZenML Models](/docs/book/.gitbook/assets/readme_mcp.gif)
-### Purpose built for machine learning with integrations to your favorite tools
-While ZenML brings a lot of value out of the box, it also integrates into your existing tooling and infrastructure without you having to be locked in.
-```python
-from bentoml._internal.bento import bento
-@step(on_failure=alert_slack, experiment_tracker="mlflow")
-def train_and_deploy(training_df: pd.DataFrame) -> bento.Bento
-	mlflow.autolog()
-	...
-	return bento
-```
-![Exploring ZenML Integrations](/docs/book/.gitbook/assets/readme_integrations.gif)
-## 🖼️ Learning
-The best way to learn about ZenML is the [docs](https://docs.zenml.io/). We recommend beginning with the [Starter Guide](https://docs.zenml.io/user-guide/starter-guide) to get up and running quickly.
-If you are a visual learner, this 11-minute video tutorial is also a great start:
-[![Introductory Youtube Video](docs/book/.gitbook/assets/readme_youtube_thumbnail.png)](https://www.youtube.com/watch?v=wEVwIkDvUPs)
-And finally, here are some other examples and use cases for inspiration:
-1. [E2E Batch Inference](examples/e2e/): Feature engineering, training, and inference pipelines for tabular machine learning.
-2. [Basic NLP with BERT](examples/e2e_nlp/): Feature engineering, training, and inference focused on NLP.
-3. [LLM RAG Pipeline with Langchain and OpenAI](https://github.com/zenml-io/zenml-projects/tree/main/llm-agents): Using Langchain to create a simple RAG pipeline.
-4. [Huggingface Model to Sagemaker Endpoint](https://github.com/zenml-io/zenml-projects/tree/main/huggingface-sagemaker): Automated MLOps on Amazon Sagemaker and HuggingFace
-5. [LLMops](https://github.com/zenml-io/zenml-projects/tree/main/llm-complete-guide): Complete guide to do LLM with ZenML
-## 📚 Learn from Books
-<div align="center">
-  <a href="https://www.amazon.com/LLM-Engineers-Handbook-engineering-production/dp/1836200072">
-    <img src="docs/book/.gitbook/assets/llm_engineering_handbook_cover.jpg" alt="LLM Engineer's Handbook Cover" width="200"/></img>
-  </a>&nbsp;&nbsp;&nbsp;&nbsp;
-  <a href="https://www.amazon.com/-/en/Andrew-McMahon/dp/1837631964">
-    <img src="docs/book/.gitbook/assets/ml_engineering_with_python.jpg" alt="Machine Learning Engineering with Python Cover" width="200"/></img>
-  </a>
-  </br></br>
-</div>
-ZenML is featured in these comprehensive guides to modern MLOps and LLM engineering. Learn how to build production-ready machine learning systems with real-world examples and best practices.
-## 🔋 Deploy ZenML
-For full functionality ZenML should be deployed on the cloud to
-enable collaborative features as the central MLOps interface for teams.
-Read more about various deployment options [here](https://docs.zenml.io/getting-started/deploying-zenml).
-Or, sign up for [ZenML Pro to get a fully managed server on a free trial](https://cloud.zenml.io/?utm_source=readme&utm_medium=referral_link&utm_campaign=cloud_promotion&utm_content=signup_link).
-## Use ZenML with VS Code
-ZenML has a [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ZenML.zenml-vscode) that allows you to inspect your stacks and pipeline runs directly from your editor. The extension also allows you to switch your stacks without needing to type any CLI commands.
-<details>
-  <summary>🖥️ VS Code Extension in Action!</summary>
-  <div align="center">
-  <img width="60%" src="/docs/book/.gitbook/assets/zenml-extension-shortened.gif" alt="ZenML Extension">
-</div>
-</details>
-## 🗺 Roadmap
-ZenML is being built in public. The [roadmap](https://zenml.io/roadmap) is a regularly updated source of truth for the ZenML community to understand where the product is going in the short, medium, and long term.
-ZenML is managed by a [core team](https://zenml.io/company) of developers that are responsible for making key decisions and incorporating feedback from the community. The team oversees feedback via various channels,
-and you can directly influence the roadmap as follows:
-- Vote on your most wanted feature on our [Discussion
-board](https://zenml.io/discussion).
-- Start a thread in our [Slack channel](https://zenml.io/slack).
-- [Create an issue](https://github.com/zenml-io/zenml/issues/new/choose) on our GitHub repo.
-## 🙌 Contributing and Community
-We would love to develop ZenML together with our community! The best way to get
-started is to select any issue from the `[good-first-issue`
-label](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22)
-and open up a Pull Request!
-If you
-would like to contribute, please review our [Contributing
-Guide](CONTRIBUTING.md) for all relevant details.
-## 🆘 Getting Help
-The first point of call should
-be [our Slack group](https://zenml.io/slack-invite/).
-Ask your questions about bugs or specific use cases, and someone from
-the [core team](https://zenml.io/company) will respond.
-Or, if you
-prefer, [open an issue](https://github.com/zenml-io/zenml/issues/new/choose) on
-our GitHub repo.
-## ⭐️ Show Your Support
-If you find ZenML helpful or interesting, please consider giving us a star on GitHub. Your support helps promote the project and lets others know that it's worth checking out.
-Thank you for your support! 🌟
-[![Star this project](https://img.shields.io/github/stars/zenml-io/zenml?style=social)](https://github.com/zenml-io/zenml/stargazers)
-## 📜 License
-ZenML is distributed under the terms of the Apache License Version 2.0.
-A complete version of the license is available in the [LICENSE](LICENSE) file in
-this repository. Any contribution made to this project will be licensed under
-the Apache License Version 2.0.
-<div>
-<p align="left">
-    <div align="left">
-      Join our <a href="https://zenml.io/slack" target="_blank">
-      <img width="18" src="https://cdn3.iconfinder.com/data/icons/logos-and-brands-adobe/512/306_Slack-512.png" alt="Slack"/>
-    <b>Slack Community</b> </a> and be part of the ZenML family.
-    </div>
-    <br />
-    <a href="https://zenml.io/features">Features</a>
-    ·
-    <a href="https://zenml.io/roadmap">Roadmap</a>
-    ·
-    <a href="https://github.com/zenml-io/zenml/issues">Report Bug</a>
-    ·
-    <a href="https://zenml.io/pro">Sign up for ZenML Pro</a>
-    ·
-    <a href="https://www.zenml.io/blog">Read Blog</a>
-    ·
-    <a href="https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22">Contribute to Open Source</a>
-    ·
-    <a href="https://github.com/zenml-io/zenml-projects">Projects Showcase</a>
-    <br />
-    <br />
-    🎉 Version 0.71.0 is out. Check out the release notes
-    <a href="https://github.com/zenml-io/zenml/releases">here</a>.
-    <br />
-    🖥️ Download our VS Code Extension <a href="https://marketplace.visualstudio.com/items?itemName=ZenML.zenml-vscode">here</a>.
-    <br />
-  </p>
-</div>

zenml-nightly 0.71.0.dev20250105__py3-none-any.whl → 0.71.0.dev20250107__py3-none-any.whl

zenml-nightly 0.71.0.dev20250105py3-none-any.whl → 0.71.0.dev20250107py3-none-any.whl