zenml-nightly 0.83.0.dev20250611__tar.gz → 0.83.0.dev20250612__tar.gz

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: zenml-nightly
-Version: 0.83.0.dev20250611
+Version: 0.83.0.dev20250612
 Summary: ZenML: Write production-ready ML code.
 License: Apache-2.0
 Keywords: machine learning,production,pipeline,mlops,devops

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "zenml-nightly"
-version = "0.83.0.dev20250611"
+version = "0.83.0.dev20250612"
 packages = [{ include = "zenml", from = "src" }]
 description = "ZenML: Write production-ready ML code."
 authors = ["ZenML GmbH <info@zenml.io>"]

zenml_nightly-0.83.0.dev20250612/src/zenml/VERSION

@@ -0,0 +1 @@
+0.83.0.dev20250612

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/artifacts/utils.py

@@ -852,7 +852,7 @@ def _load_artifact_store(
             StackComponent.from_model(artifact_store_model),
         )
     except ImportError:
-        link = "https://docs.zenml.io/stack-components/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
+        link = "https://docs.zenml.io/stacks/stack-components/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
         raise NotImplementedError(
             f"Artifact store '{artifact_store_model.name}' could not be "
             f"instantiated. This is likely because the artifact store's "
@@ -950,7 +950,7 @@ def _load_file_from_artifact_store(
         raise e
     except Exception as e:
         logger.exception(e)
-        link = "https://docs.zenml.io/stack-components/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
+        link = "https://docs.zenml.io/stacks/stack-components/artifact-stores/custom#enabling-artifact-visualizations-with-custom-artifact-stores"
         raise NotImplementedError(
             f"File '{uri}' could not be loaded because the underlying artifact "
             f"store '{artifact_store.name}' could not open the file. This is "

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/cli/__init__.py

@@ -80,7 +80,7 @@ You can also pass in a directory path manually using the
 zenml init --path /path/to/dir
 ```
 
-If you wish to use one of [the available ZenML project templates](https://docs.zenml.io/how-to/project-setup-and-management/collaborate-with-team/project-templates)
+If you wish to use one of [the available ZenML project templates](https://docs.zenml.io/user-guides/best-practices/project-templates)
 to generate a ready-to-use project scaffold in your repository, you can do so by
 passing the ``--template`` option:
 
@@ -232,7 +232,7 @@ and `and` keywords.
 Artifact Stores
 ---------------
 
-In ZenML, [the artifact store](https://docs.zenml.io/stack-components/artifact-stores)
+In ZenML, [the artifact store](https://docs.zenml.io/stacks/stack-components/artifact-stores)
 is where all the inputs and outputs of your pipeline steps are stored. By
 default, ZenML initializes your repository with an artifact store with
 everything kept on your local machine. You can get a better understanding
@@ -327,7 +327,7 @@ zenml artifact-store --help
 Orchestrators
 -------------
 
-An [orchestrator](https://docs.zenml.io/stack-components/orchestrators)
+An [orchestrator](https://docs.zenml.io/stacks/stack-components/orchestrators)
 is a special kind of backend that manages the running of each step of the
 pipeline. Orchestrators administer the actual pipeline runs. By default,
 ZenML initializes your repository with an orchestrator that runs everything
@@ -422,7 +422,7 @@ zenml orchestrators --help
 Container Registries
 --------------------
 
-[The container registry](https://docs.zenml.io/stack-components/container-registries)
+[The container registry](https://docs.zenml.io/stacks/stack-components/container-registries)
 is where all the images that are used by a container-based orchestrator are
 stored. To get a better understanding regarding container registries, use
 the command:
@@ -517,7 +517,7 @@ zenml container-registry --help
 Data Validators
 ---------------
 
-In ZenML, [data validators](https://docs.zenml.io/stack-components/data-validators)
+In ZenML, [data validators](https://docs.zenml.io/stacks/stack-components/data-validators)
 help you profile and validate your data.
 
 By default, a default ZenML local stack will not register a data validator. If
@@ -604,7 +604,7 @@ zenml data-validator --help
 Experiment Trackers
 -------------------
 
-[Experiment trackers](https://docs.zenml.io/stack-components/experiment-trackers)
+[Experiment trackers](https://docs.zenml.io/stacks/stack-components/experiment-trackers)
  let you track your ML experiments by logging the parameters
 and allow you to compare between different runs. To get a better
 understanding regarding experiment trackers, use the command:
@@ -700,7 +700,7 @@ zenml experiment-tracker --help
 Model Deployers
 ---------------
 
-[Model deployers](https://docs.zenml.io/stack-components/model-deployers)
+[Model deployers](https://docs.zenml.io/stacks/stack-components/model-deployers)
 are stack components responsible for online model serving. They are responsible
 for deploying models to a remote server. Model deployers also act as a registry
 for models that are served with ZenML. To get a better understanding regarding
@@ -837,7 +837,7 @@ zenml model-deployer --help
 Step Operators
 --------------
 
-[Step operators](https://docs.zenml.io/stack-components/step-operators)
+[Step operators](https://docs.zenml.io/stacks/stack-components/step-operators)
 allow you to run individual steps in a custom environment different from the
 default one used by your active orchestrator. One example use-case is to run a
 training step of your pipeline in an environment with GPUs available. To get
@@ -932,7 +932,7 @@ zenml step-operator --help
 Alerters
 --------
 
-In ZenML, [alerters](https://docs.zenml.io/stack-components/alerters)
+In ZenML, [alerters](https://docs.zenml.io/stacks/stack-components/alerters)
 allow you to send alerts from within your pipeline.
 
 By default, a default ZenML local stack will not register an alerter. If
@@ -1017,7 +1017,7 @@ zenml alerter --help
 Feature Stores
 --------------
 
-[Feature stores](https://docs.zenml.io/stack-components/feature-stores)
+[Feature stores](https://docs.zenml.io/stacks/stack-components/feature-stores)
 allow data teams to serve data via an offline store and an online low-latency
 store where data is kept in sync between the two. To get a better understanding
 regarding feature stores, use the command:
@@ -1114,7 +1114,7 @@ zenml feature-store --help
 Annotators
 ----------
 
-[Annotators](https://docs.zenml.io/stack-components/annotators)
+[Annotators](https://docs.zenml.io/stacks/stack-components/annotators)
 enable the use of data annotation as part of your ZenML stack and pipelines.
 
 By default, a default ZenML local stack will not register an annotator. If
@@ -1206,7 +1206,7 @@ zenml annotator --help
 Image Builders
 --------------
 
-In ZenML, [image builders](https://docs.zenml.io/stack-components/image-builders)
+In ZenML, [image builders](https://docs.zenml.io/stacks/stack-components/image-builders)
 allow you to build container images such
 that your machine-learning pipelines and steps can be executed in remote
 environments.
@@ -1295,7 +1295,7 @@ zenml image-builder --help
 Model Registries
 ----------------
 
-[Model registries](https://docs.zenml.io/stack-components/model-registries)
+[Model registries](https://docs.zenml.io/stacks/stack-components/model-registries)
 are centralized repositories that facilitate the collaboration and management
 of machine learning models. To get a better understanding regarding model
 registries as a concept, use the command:
@@ -1985,7 +1985,7 @@ Secrets management
 ------------------
 
 ZenML offers a way to [securely store secrets associated with your other
-stack components and infrastructure](https://docs.zenml.io/getting-started/deploying-zenml/secret-management).
+stack components and infrastructure](https://docs.zenml.io/deploying-zenml/deploying-zenml/secret-management).
 A ZenML Secret is a collection or grouping of key-value pairs stored by the
 ZenML secrets store. ZenML Secrets are identified by a unique name which
 allows you to fetch or reference them in your pipelines and stacks.
@@ -2082,7 +2082,7 @@ challenge in configuring uninterrupted, secure access to infrastructure
 resources. In ZenML, Service Connectors streamline this process by abstracting
 away the complexity of authentication and help you connect your stack to your
 resources. You can find the full docs on the ZenML service connectors
-[here](https://docs.zenml.io/how-to/infrastructure-deployment/auth-management).
+[here](https://docs.zenml.io/stacks/service-connectors/auth-management).
 
 The ZenML CLI features a variety of commands to help you manage your service
 connectors. First of all, to explore all the types of service connectors
@@ -2112,7 +2112,7 @@ zenml service-connector register SERVICE_CONNECTOR_NAME \
 ```
 
 For more details on how to create a service connector, please refer to our
-[docs](https://docs.zenml.io/how-to/infrastructure-deployment/auth-management).
+[docs](https://docs.zenml.io/stacks/service-connectors/auth-management).
 
 To check if your service connector is registered properly, you can `verify` it.
 By doing this, you can both check if it is configured correctly and also, you
@@ -2366,7 +2366,7 @@ defining the pipeline is not in your current directory, the module path consists
 of the full path to the file, separated by dots, e.g.
 `some_directory.some_file.my_pipeline`.
 
-To [build Docker images for your pipeline](https://docs.zenml.io/how-to/infrastructure-deployment/customize-docker-builds)
+To [build Docker images for your pipeline](https://docs.zenml.io/concepts/containerization)
 without actually running the pipeline, use:
 
 ```bash
@@ -2429,7 +2429,7 @@ Tagging your resources with ZenML
 ---------------------------------
 
 When you are using ZenML, you can [use tags to organize and categorize your
-assets](https://docs.zenml.io/how-to/handle-data-artifacts/tagging).
+assets](https://docs.zenml.io/concepts/tags).
 This way, you can streamline your workflows and enhance the discoverability of
 your resources more easily.
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/cli/base.py

@@ -264,7 +264,7 @@ def init(
         f"will only take effect when you're running ZenML from the initialized "
         f"repository root, or from a subdirectory. For more information on "
         f"repositories and configurations, please visit "
-        f"https://docs.zenml.io/user-guides/production-guide/understand-stacks."
+        f"https://docs.zenml.io/user-guides/production-guide/understand-stacks"
     )
 
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/cli/server.py

@@ -413,7 +413,7 @@ def connect(
             "filesystem and is no longer supported. The web login workflow will "
             "be used instead. An alternative for non-interactive environments "
             "is to create and use a service account API key (see "
-            "https://docs.zenml.io/how-to/manage-zenml-server/connecting-to-zenml/connect-with-a-service-account "
+            "https://docs.zenml.io/deploying-zenml/connecting-to-zenml/connect-with-a-service-account "
             "for more information)."
         )
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/cli/stack.py

@@ -276,7 +276,7 @@ def register_stack(
                 "ZenML needs to be accessible from the cloud provider to allow "
                 "the stack and its components to be registered automatically. "
                 "Please deploy ZenML in a remote environment as described in "
-                "the documentation: https://docs.zenml.io/getting-started/deploying-zenml "
+                "the documentation: https://docs.zenml.io/deploying-zenml/deploying-zenml "
                 "or use a managed ZenML Pro server instance for quick access "
                 "to this feature and more: https://www.zenml.io/pro"
             )
@@ -1515,7 +1515,7 @@ def deploy(
             "ZenML needs to be accessible from the cloud provider to allow the "
             "stack and its components to be registered automatically. "
             "Please deploy ZenML in a remote environment as described in the "
-            "documentation: https://docs.zenml.io/getting-started/deploying-zenml "
+            "documentation: https://docs.zenml.io/deploying-zenml/deploying-zenml "
             "or use a managed ZenML Pro server instance for quick access to "
             "this feature and more: https://www.zenml.io/pro"
         )

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/config/compiler.py

@@ -598,7 +598,7 @@ class Compiler:
                 f"no steps. Please make sure that your steps are decorated "
                 "with `@step` and that at least one step is called within the "
                 "pipeline. For more information, see "
-                "https://docs.zenml.io/user-guides/starter-guide."
+                "https://docs.zenml.io/user-guides/starter-guide"
             )
 
         additional_spec_args: Dict[str, Any] = {

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/config/secret_reference_mixin.py

@@ -66,7 +66,7 @@ class SecretReferenceMixin(BaseModel):
                         "but future versions of ZenML will require you to pass "
                         "in sensitive information as secrets. Check out the "
                         "documentation on how to configure values with secrets "
-                        "here: https://docs.zenml.io/getting-started/deploying-zenml/secret-management"
+                        "here: https://docs.zenml.io/deploying-zenml/deploying-zenml/secret-management"
                     )
                 continue
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/integrations/aws/flavors/sagemaker_orchestrator_flavor.py

@@ -190,7 +190,7 @@ class SagemakerOrchestratorConfig(
         scheduler_role: The ARN of the IAM role that will be assumed by
             the EventBridge service to launch Sagemaker pipelines
             (For more details regarding the required permissions, please check:
-            https://docs.zenml.io/stack-components/orchestrators/sagemaker#required-iam-permissions-for-schedules)
+            https://docs.zenml.io/stacks/stack-components/orchestrators/sagemaker#required-iam-permissions-for-schedules)
         aws_access_key_id: The AWS access key ID to use to authenticate to AWS.
             If not provided, the value from the default AWS config will be used.
         aws_secret_access_key: The AWS secret access key to use to authenticate

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/integrations/aws/orchestrators/sagemaker_orchestrator.py

@@ -693,7 +693,7 @@ class SagemakerOrchestrator(ContainerizedOrchestrator):
                         "your client side credentials that you are "
                         "is not configured correctly to schedule sagemaker "
                         "pipelines. For more information, please check:"
-                        "https://docs.zenml.io/stack-components/orchestrators/sagemaker#required-iam-permissions-for-schedules"
+                        "https://docs.zenml.io/stacks/stack-components/orchestrators/sagemaker#required-iam-permissions-for-schedules"
                     )
             else:
                 scheduler_role_arn = self.config.scheduler_role

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/integrations/gcp/orchestrators/vertex_orchestrator.py

@@ -913,7 +913,7 @@ class VertexOrchestrator(ContainerizedOrchestrator, GoogleCredentialsMixin):
                     "set or set to 0. The accelerator type will be ignored. "
                     "To fix this warning, either remove the specified "
                     "accelerator type or set the `gpu_count` using the "
-                    "ResourceSettings (https://docs.zenml.io/how-to/advanced-topics/training-with-gpus)."
+                    "ResourceSettings (https://docs.zenml.io/user-guides/tutorial/distributed-training)."
                 )
 
         return dynamic_component

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/integrations/neptune/experiment_trackers/run_state.py

@@ -171,7 +171,7 @@ def get_neptune_run() -> "Run":
             "Unable to get neptune run: The experiment tracker has not been "
             "initialized. To solve this, make sure you use the experiment "
             "tracker in your step. See "
-            "https://docs.zenml.io/stack-components/experiment-trackers/neptune#how-do-you-use-it "
+            "https://docs.zenml.io/stacks/stack-components/experiment-trackers/neptune#how-do-you-use-it "
             "for more information."
         )
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/materializers/base_materializer.py

@@ -68,7 +68,7 @@ class BaseMaterializerMeta(type):
                     f"Invalid materializer class '{name}'. When creating a "
                     f"custom materializer, make sure to specify at least one "
                     f"type in its ASSOCIATED_TYPES class variable.",
-                    url="https://docs.zenml.io/how-to/handle-data-artifacts/handle-custom-data-types",
+                    url="https://docs.zenml.io/concepts/artifacts/materializers",
                 )
 
             # Validate associated artifact type.
@@ -83,7 +83,7 @@ class BaseMaterializerMeta(type):
                         f"custom materializer, make sure to specify a valid "
                         f"artifact type in its ASSOCIATED_ARTIFACT_TYPE class "
                         f"variable.",
-                        url="https://docs.zenml.io/how-to/handle-data-artifacts/handle-custom-data-types",
+                        url="https://docs.zenml.io/concepts/artifacts/materializers",
                     )
 
             # Validate associated data types.
@@ -92,7 +92,7 @@ class BaseMaterializerMeta(type):
                     raise MaterializerInterfaceError(
                         f"Associated type {associated_type} for materializer "
                         f"{name} is not a class.",
-                        url="https://docs.zenml.io/how-to/handle-data-artifacts/handle-custom-data-types",
+                        url="https://docs.zenml.io/concepts/artifacts/materializers",
                     )
 
             # Register the materializer.

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/materializers/cloudpickle_materializer.py

@@ -102,7 +102,7 @@ class CloudpickleMaterializer(BaseMaterializer):
                 "the artifacts cannot be loaded when running with a different "
                 "Python version. Please consider implementing a custom "
                 f"materializer for type `{type(data)}` according to the "
-                "instructions at https://docs.zenml.io/how-to/handle-data-artifacts/handle-custom-data-types"
+                "instructions at https://docs.zenml.io/concepts/artifacts/materializers"
             )
 
         # save python version for validation on loading

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/model/utils.py

@@ -58,7 +58,7 @@ def log_model_metadata(
         "The `log_model_metadata` function is deprecated and will soon be "
         "removed. Instead, you can consider using: "
         "`log_metadata(metadata={...}, infer_model=True)` instead. For more "
-        "info: https://docs.zenml.io/how-to/model-management-metrics/track-metrics-metadata/attach-metadata-to-a-model"
+        "info: https://docs.zenml.io/concepts/metadata#attaching-metadata-to-models"
     )
 
     from zenml import log_metadata

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/orchestrators/base_orchestrator.py

@@ -61,7 +61,7 @@ class BaseOrchestratorConfig(StackComponentConfig):
                     "The 'custom_docker_base_image_name' field has been "
                     "deprecated. To use a custom base container image with your "
                     "orchestrators, please use the DockerSettings in your "
-                    "pipeline (see https://docs.zenml.io/how-to/infrastructure-deployment/customize-docker-builds)."
+                    "pipeline (see https://docs.zenml.io/concepts/containerization)."
                 )
 
         return data

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/orchestrators/utils.py

@@ -182,7 +182,7 @@ def get_config_environment_vars(
                         "service account API key to authenticate to the ZenML "
                         "server instead of your regular user account. For more "
                         "information, see "
-                        "https://docs.zenml.io/how-to/manage-zenml-server/connecting-to-zenml/connect-with-a-service-account"
+                        "https://docs.zenml.io/deploying-zenml/connecting-to-zenml/connect-with-a-service-account"
                     )
 
                 # The schedule, pipeline run or step run credentials are scoped to

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/pipelines/pipeline_definition.py

@@ -686,7 +686,7 @@ To avoid this consider setting pipeline parameters only in one place (config or
                     f"Stack {stack.name} does not support scheduling. "
                     "Not all orchestrator types support scheduling, "
                     "kindly consult with "
-                    "https://docs.zenml.io/how-to/build-pipelines/schedule-a-pipeline "
+                    "https://docs.zenml.io/concepts/steps_and_pipelines/scheduling "
                     "for details."
                 )
             if schedule.name:

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/service_connectors/service_connector_utils.py

@@ -60,9 +60,9 @@ def _raise_specific_cloud_exception_if_needed(
     orchestrators: List[ResourcesInfo],
     container_registries: List[ResourcesInfo],
 ) -> None:
-    AWS_DOCS = "https://docs.zenml.io/how-to/infrastructure-deployment/auth-management/aws-service-connector"
-    GCP_DOCS = "https://docs.zenml.io/how-to/infrastructure-deployment/auth-management/gcp-service-connector"
-    AZURE_DOCS = "https://docs.zenml.io/how-to/infrastructure-deployment/auth-management/azure-service-connector"
+    AWS_DOCS = "https://docs.zenml.io/stacks/service-connectors/connector-types/aws-service-connector"
+    GCP_DOCS = "https://docs.zenml.io/stacks/service-connectors/connector-types/gcp-service-connector"
+    AZURE_DOCS = "https://docs.zenml.io/stacks/service-connectors/connector-types/azure-service-connector"
 
     if not artifact_stores:
         error_msg = (

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/stack/stack_component.py

@@ -106,7 +106,7 @@ class StackComponentConfig(BaseModel, ABC):
                         "in sensitive information as secrets. Check out the "
                         "documentation on how to configure your stack "
                         "components with secrets here: "
-                        "https://docs.zenml.io/getting-started/deploying-zenml/secret-management"
+                        "https://docs.zenml.io/deploying-zenml/deploying-zenml/secret-management"
                     )
                 continue
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/steps/entrypoint_function_utils.py

@@ -83,7 +83,7 @@ class StepArtifact:
             "you're trying to unpack the return value of your step but the "
             "step only returns a single artifact. For more information on how "
             "to add type annotations to your step to indicate multiple "
-            "artifacts visit https://docs.zenml.io/how-to/build-pipelines/step-output-typing-and-annotation#type-annotations."
+            "artifacts visit https://docs.zenml.io/concepts/steps_and_pipelines#multiple-return-values."
         )
 
 

{zenml_nightly-0.83.0.dev20250611 → zenml_nightly-0.83.0.dev20250612}/src/zenml/zen_stores/rest_zen_store.py

@@ -4454,7 +4454,7 @@ class RestZenStore(BaseZenStore):
                         f"`zenml login {self.url}` to "
                         "re-authenticate to the server or authenticate using "
                         "an API key. See "
-                        "https://docs.zenml.io/how-to/project-setup-and-management/connecting-to-zenml/connect-with-a-service-account "
+                        "https://docs.zenml.io/deploying-zenml/connecting-to-zenml/connect-with-a-service-account "
                         "for more information."
                     )
                     # Clear the current token from the credentials store to

zenml_nightly-0.83.0.dev20250611/src/zenml/VERSION

@@ -1 +0,0 @@
-0.83.0.dev20250611