Release 0.18.11

CITATION.cff

@@ -45,6 +45,6 @@ authors:
 - family-names: Theisen
   given-names: Merel
 title: Kedro
-version: 0.18.10
-date-released: 2023-06-08
+version: 0.18.11
+date-released: 2023-07-03
 url: https://github.com/kedro-org/kedro

RELEASE.md

@@ -9,7 +9,19 @@
 
 ## Migration guide from Kedro 0.18.* to 0.19.*
 
-# Upcoming Release 0.18.11
+# Upcoming Release 0.18.12
+
+## Major features and improvements
+
+## Bug fixes and other changes
+
+## Documentation changes
+
+## Breaking changes to the API
+
+## Upcoming deprecations for Kedro 0.19.0
+
+# Release 0.18.11
 
 ## Major features and improvements
 * Added `databricks-iris` as an official starter.
@@ -19,11 +31,21 @@
 * Make `kedro micropkg package` accept `--verbose`.
 
 ## Documentation changes
-* Added documentation for developing a Kedro project using a Databricks workspace.
-
-## Breaking changes to the API
+* Significant improvements to the documentation that covers working with Databricks and Kedro, including a new page for workspace-only development, and a guide to choosing the best workflow for your use case.
 
 ## Upcoming deprecations for Kedro 0.19.0
+* Renamed dataset and error classes, in accordance with the [Kedro lexicon](https://github.com/kedro-org/kedro/wiki/Kedro-documentation-style-guide#kedro-lexicon). Dataset classes ending with "DataSet" and error classes starting with "DataSet" are deprecated and will be removed in 0.19.0. Note that all of the below classes are also importable from `kedro.io`; only the module where they are defined is listed as the location.
+
+| Type                        | Deprecated Alias            | Location                       |
+| --------------------------- | --------------------------- | ------------------------------ |
+| `CachedDataset`             | `CachedDataSet`             | `kedro.io.cached_dataset`      |
+| `LambdaDataset`             | `LambdaDataSet`             | `kedro.io.lambda_dataset`      |
+| `IncrementalDataset`        | `IncrementalDataSet`        | `kedro.io.partitioned_dataset` |
+| `MemoryDataset`             | `MemoryDataSet`             | `kedro.io.memory_dataset`      |
+| `PartitionedDataset`        | `PartitionedDataSet`        | `kedro.io.partitioned_dataset` |
+| `DatasetError`              | `DataSetError`              | `kedro.io.core`                |
+| `DatasetAlreadyExistsError` | `DataSetAlreadyExistsError` | `kedro.io.core`                |
+| `DatasetNotFoundError`      | `DataSetNotFoundError`      | `kedro.io.core`                |
 
 # Release 0.18.10
 

docs/source/configuration/advanced_configuration.md

@@ -238,7 +238,7 @@ data:
 Since both of the file names (`parameters.yml` and `parameters_globals.yml`) match the config pattern for parameters, the `OmegaConfigLoader` will load the files and resolve the placeholders correctly.
 
 #### Catalog
-From Kedro `0.18.10` templating also works for catalog files. To enable templating in the catalog you need to ensure that the template values are within the catalog files or the name of the file that contains the template values follows the same config pattern specified for catalogs.
+From Kedro `0.18.11` templating also works for catalog files. To enable templating in the catalog you need to ensure that the template values are within the catalog files or the name of the file that contains the template values follows the same config pattern specified for catalogs.
 By default, the config pattern for catalogs is: `["catalog*", "catalog*/**", "**/catalog*"]`.
 
 Additionally, any template values in the catalog need to start with an underscore `_`. This is because of how catalog entries are validated. Templated values will neither trigger a key duplication error nor appear in the resulting configuration dictionary.

docs/source/development/commands_reference.md

@@ -114,7 +114,7 @@ Returns output similar to the following, depending on the version of Kedro used
 | |/ / _ \/ _` | '__/ _ \
 |   <  __/ (_| | | | (_) |
 |_|\_\___|\__,_|_|  \___/
-v0.18.10
+v0.18.11
 
 Kedro is a Python framework for
 creating reproducible, maintainable

docs/source/extend_kedro/plugins.md

@@ -84,7 +84,7 @@ setup(
 After that you can use this starter with `kedro new --starter=test_plugin_starter`.
 
 ```{note}
-If your starter lives on a git repository, by default Kedro attempts to use a tag or branch labelled with your version of Kedro, e.g. `0.18.10`. This means that you can host different versions of your starter template on the same repository, and the correct one will automatically be used. If you do not wish to follow this structure, you should override it with the `checkout` flag, e.g. `kedro new --starter=test_plugin_starter --checkout=main`.
+If your starter lives on a git repository, by default Kedro attempts to use a tag or branch labelled with your version of Kedro, e.g. `0.18.11`. This means that you can host different versions of your starter template on the same repository, and the correct one will automatically be used. If you do not wish to follow this structure, you should override it with the `checkout` flag, e.g. `kedro new --starter=test_plugin_starter --checkout=main`.
 ```
 
 ## Working with `click`

docs/source/tutorial/tutorial_template.md

@@ -49,7 +49,7 @@ pytest-mock>=1.7.1, <2.0
 pytest~=7.2
 
 # Kedro dependencies and datasets to work with different data formats (including CSV, Excel, and Parquet)
-kedro~=0.18.10
+kedro~=0.18.11
 kedro-datasets[pandas.CSVDataSet, pandas.ExcelDataSet, pandas.ParquetDataSet]~=1.1
 kedro-telemetry~=0.2.0
 kedro-viz~=6.0 # Visualise pipelines

kedro/__init__.py

@@ -3,4 +3,4 @@
 configuration and pipeline assembly.
 """
 
-__version__ = "0.18.10"
+__version__ = "0.18.11"