he Post-execution workflow has changed as follows:The get_pipelines and get_pipeline methods have been moved out of the Repository (i.e. the new Client ) class and lie directly in the post_execution module now. To use the user has to do:

from zenml.post_execution import get_pipelines, get_pipeline

New methods to directly get a run have been introduced: get_run and get_unlisted_runs method has been introduced to get unlisted runs.

Usage remains largely similar. Please read the new docs for post-execution to inform yourself of what further has changed.

How to migrate: Replace all post-execution workflows from the paradigm of Repository.get_pipelines or Repository.get_pipeline_run to the corresponding post_execution methods.

📡Future Changes

While this rehaul is big and will break previous releases, we do have some more work left to do. However we also expect this to be the last big rehaul of ZenML before our 1.0.0 release, and no other release will be so hard breaking as this one. Currently planned future breaking changes are:

Following the metadata store, the secrets manager stack component might move out of the stack.

ZenML StepContext might be deprecated.

🐞 Reporting Bugs

While we have tried our best to document everything that has changed, we realize that mistakes can be made and smaller changes overlooked. If this is the case, or you encounter a bug at any time, the ZenML core team and community are available around the clock on the growing Slack community.

For bug reports, please also consider submitting a GitHub Issue.

Lastly, if the new changes have left you desiring a feature, then consider adding it to our public feature voting board. Before doing so, do check what is already on there and consider upvoting the features you desire the most.

PreviousMigration guide

NextMigration guide 0.23.0 → 0.30.0

Last updated 15 days ago