zenml-nightly 0.83.1.dev20250710__py3-none-any.whl → 0.84.0.dev20250712__py3-none-any.whl

zenml/zen_stores/migrations/versions/0.84.0_release.py

@@ -0,0 +1,23 @@
+"""Release [0.84.0].
+
+Revision ID: 0.84.0
+Revises: 360fa84718bf
+Create Date: 2025-07-10 14:07:30.176139
+
+"""
+
+# revision identifiers, used by Alembic.
+revision = "0.84.0"
+down_revision = "360fa84718bf"
+branch_labels = None
+depends_on = None
+
+
+def upgrade() -> None:
+    """Upgrade database schema and/or data, creating a new revision."""
+    pass
+
+
+def downgrade() -> None:
+    """Downgrade database schema and/or data back to the previous revision."""
+    pass

zenml/zen_stores/sql_zen_store.py

@@ -5744,7 +5744,9 @@ class SqlZenStore(BaseZenStore):
 
             log_entry = LogsSchema(
                 uri=pipeline_run.logs.uri,
-                source=pipeline_run.logs.source,
+                # TODO: Remove fallback when not supporting
+                # clients <0.84.0 anymore
+                source=pipeline_run.logs.source or "client",
                 pipeline_run_id=new_run.id,
                 artifact_store_id=pipeline_run.logs.artifact_store_id,
             )
@@ -6152,7 +6154,9 @@ class SqlZenStore(BaseZenStore):
                         # Create the log entry
                         log_entry = LogsSchema(
                             uri=log_request.uri,
-                            source=log_request.source,
+                            # TODO: Remove fallback when not supporting
+                            # clients <0.84.0 anymore
+                            source=log_request.source or "orchestrator",
                             pipeline_run_id=existing_run.id,
                             artifact_store_id=log_request.artifact_store_id,
                         )
@@ -9041,7 +9045,9 @@ class SqlZenStore(BaseZenStore):
 
                 log_entry = LogsSchema(
                     uri=step_run.logs.uri,
-                    source=step_run.logs.source,
+                    # TODO: Remove fallback when not supporting
+                    # clients <0.84.0 anymore
+                    source=step_run.logs.source or "execution",
                     step_run_id=step_schema.id,
                     artifact_store_id=step_run.logs.artifact_store_id,
                 )

{zenml_nightly-0.83.1.dev20250710.dist-info → zenml_nightly-0.84.0.dev20250712.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: zenml-nightly
-Version: 0.83.1.dev20250710
+Version: 0.84.0.dev20250712
 Summary: ZenML: Write production-ready ML code.
 License: Apache-2.0
 Keywords: machine learning,production,pipeline,mlops,devops
@@ -198,9 +198,9 @@ Description-Content-Type: text/markdown
 
 ![No MLOps for modern AI](docs/book/.gitbook/assets/readme_problem.png)
 
-You're an ML engineer. You've perfected deploying scikit-learn models and wrangling TensorFlow jobs. Your MLOps stack is dialed in. But now, you're being asked to build and ship AI agents, and suddenly your trusted toolkit is starting to crack.
+You're an ML engineer. You've perfected deploying `scikit-learn` models and wrangling PyTorch jobs. Your MLOps stack is dialed in. But now, you're being asked to build and ship AI agents, and suddenly your trusted toolkit is starting to crack.
 
-- **The Adaptation Struggle:** Your MLOps habits—rigorous testing, versioning, CI/CD—don’t map cleanly onto agent development. How do you version a prompt? How do you regression test a non-deterministic system? The tools that gave you confidence for models now create friction for agents.
+- **The Adaptation Struggle:** Your MLOps habits (rigorous testing, versioning, CI/CD) don’t map cleanly onto agent development. How do you version a prompt? How do you regression test a non-deterministic system? The tools that gave you confidence for models now create friction for agents.
 
 - **The Divided Stack:** To cope, teams are building a second, parallel stack just for LLM-based systems. Now you’re maintaining two sets of tools, two deployment pipelines, and two mental models. Your classical models live in one world, your agents in another. It's expensive, complex, and slows everyone down.
 
@@ -328,7 +328,7 @@ results = compare_architectures(
 **Friday: Ship with Confidence**
 ```python
 # Deploy the new agent with the same command you use for ML models
-zenml stack deploy agent-prod --model="customer_service:challenger"
+python agent_deployment.py --env=prod --model="customer_service:challenger"
 ```
 </details>
 
@@ -338,7 +338,8 @@ zenml stack deploy agent-prod --model="customer_service:challenger"
 
 ```bash
 # You know this drill
-pip install "zenml[llm]"  # Includes LangChain, LlamaIndex integrations
+pip install zenml  # Includes LangChain, LlamaIndex integrations
+zenml integration install langchain llamaindex
 
 # Initialize (your ML pipelines still work!)
 zenml init
@@ -438,25 +439,10 @@ ZenML is featured in these comprehensive guides to production AI systems.
 
 ## 🤝 Join ML Engineers Building the Future of AI
 
-**You're Not Alone:**
-- 💬 [Slack Community](https://zenml.io/slack) - 3000+ ML engineers building with ZenML.
-- 🐛 [GitHub Issues](https://github.com/zenml-io/zenml/issues) - Bug reports and feature requests.
-- 📧 [Enterprise Support](https://zenml.io/pro) - SLAs, dedicated support, professional services.
-
-**Real Engineers, Real Stories:**
-> "Same platform for our sklearn models and our RAG pipeline. DevOps loves us now."
-> - ML Platform Lead, European Bank
-
-> "We went from 'YOLO prompt updates' to proper evaluation pipelines. Game changer."
-> - Senior ML Engineer, Fortune 500 Retailer
-
-> "Finally, I can explain to my PM why agent v2 is actually worse than v1. With data!"
-> - Staff Engineer, Series B Startup
-
 **Contribute:**
 - 🌟 [Star us on GitHub](https://github.com/zenml-io/zenml/stargazers) - Help others discover ZenML
 - 🤝 [Contributing Guide](CONTRIBUTING.md) - Start with [`good-first-issue`](https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+user%3Azenml-io+label%3A%22good+first+issue%22)
-- 💻 [Write Integrations](https://docs.zenml.io/how-to/stack-deployment/implement-a-custom-integration) - Add your favorite tools
+- 💻 [Write Integrations](https://github.com/zenml-io/zenml/blob/main/src/zenml/integrations/README.md) - Add your favorite tools
 
 **Stay Updated:**
 - 🗺 [Public Roadmap](https://zenml.io/roadmap) - See what's coming next
@@ -466,7 +452,7 @@ ZenML is featured in these comprehensive guides to production AI systems.
 ## ❓ FAQs from ML Engineers Like You
 
 **Q: "Do I need to rewrite my agents or models to use ZenML?"**
-A: No. Wrap your existing code in a `@step`. Keep using Scikit-Learn, PyTorch, LangGraph, LlamaIndex, or raw API calls. ZenML orchestrates your tools, it doesn't replace them.
+A: No. Wrap your existing code in a `@step`. Keep using `scikit-learn`, PyTorch, LangGraph, LlamaIndex, or raw API calls. ZenML orchestrates your tools, it doesn't replace them.
 
 **Q: "How is this different from LangSmith/Langfuse?"**
 A: They provide excellent observability for LLM applications. We orchestrate the **full MLOps lifecycle for your entire AI stack**. With ZenML, you manage both your classical ML models and your AI agents in one unified framework, from development and evaluation all the way to production deployment.
@@ -497,3 +483,4 @@ Install from [VS Code Marketplace](https://marketplace.visualstudio.com/items?it
 
 ZenML is distributed under the terms of the Apache License Version 2.0. See
 [LICENSE](LICENSE) for details.
+