0.46.1 [YANKED]

THIS RELEASE HAS BEEN YANKED

• Due to an unforeseen alembic migration issue and missing dashboard, this release has been yanked
• 0.47.0 is out to fix the bugs that have been uncovered

0.46.1

The 0.46.1 release introduces support for Service Accounts and API Keys that
can be used to authenticate with the ZenML server from environments that do not
support the web login flow, such as CI/CD environments, for example.

Also included in this release are some documentation updates and bug fixes,
notably moving the database migration logic deployed with the Helm chart out of
the init containers and into a Kubernetes Job, which makes it possible to scale
out the ZenML server deployments without the risk of running into database
migration conflicts.

What's Changed

• Small improvements to Hub docs page by @strickvl in #2015
• Pin OpenAI integration to <1.0.0 by @strickvl in #2027
• Make error message nicer for when two artifacts that share a prefix are found by @strickvl in #2023
• Move db-migration to job instead of init-container to allow replicas by @safoinme in #2021
• Fix stuck/broken CI by @strickvl in #2032
• Increase step.source_code Cut-Off Limit by @fa9r in #2025
• Improve artifact linkage logging in MCP by @avishniakov in #2016
• Upgrade feast so apidocs don't fail no mo by @AlexejPenner in #2028
• Remove NumPy Visualizations for 2D Arrays by @fa9r in #2033
• Fix user activation bug by @stefannica in #2037
• Remove create_new_model_version arg of ModelConfig by @avishniakov in #2030
• Extend the wait period in between PyPi package publication and Docker image building for releases by @strickvl in #2029
• Make zenml up prefill username when launching dashboard by @strickvl in #2024
• Add warning when artifact store cannot be loaded by @strickvl in #2011
• Add extra config to Kaniko docs by @safoinme in #2019
• ZenML API Keys and Service Accounts by @stefannica in #1840

Full Changelog: 0.46.0...0.46.1