Dmitry Sorokin
06/04/2024, 11:07 AMraise_errors
argument to find_pipelines
. If True
, the first pipeline for which autodiscovery fails will cause an error to be raised. The default behaviour is still to raise a warning for each failing pipeline.
• It is now possible to use Kedro without having rich
installed.
• Updated custom logging behavior: conf/logging.yml
will be used if it exists and KEDRO_LOGGING_CONFIG
is not set; otherwise, default_logging.yml
will be used.
• Updated the kedro-telemetry
to generate a unique UUID for each user and added support for python 3.12.
🪲 Bug fixes and other changes
• User defined catch-all dataset factory patterns now override the default pattern provided by the runner.
• Removed arbitrary upper bound for s3fs
in kedro-datasets
.
• NetCDFDataset
support for NetCDF4 via engine="netcdf4"
and engine="h5netcdf"
💥 Upcoming deprecations for Kedro 0.20.0
• All micro-packaging commands (kedro micropkg pull
, kedro micropkg package
) are deprecated and will be removed in Kedro 0.20.0. If you are an active user and are impacted by this deprecation, please leave a comment here explaining your use case.
✍🏼 Documentation changes
• Improved documentation for custom starters
• Added a new docs section on deploying Kedro project on AWS Airflow MWAA
• Detailed instructions on using globals
and runtime_params
with the OmegaConfigLoader
Read the complete release notes for kedro, kedro-datasets, and kedro-telemetry on GitHub
Thanks a lot to our community contributors @Dominik Zalewski, cleeks and @Charles Guan ✨
We welcome every community contribution, large or small. See what we're working on now and report bugs or suggest future features.
Until next time,
The Kedro Team 💛