-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.18.2 #1695
Release 0.18.2 #1695
Conversation
Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com>
docs/source/extend_kedro/plugins.md
Outdated
After that you can use this starter with `kedro new --starter=test_plugin_starter --checkout=main`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After that you can use this starter with `kedro new --starter=test_plugin_starter --checkout=main`. | |
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.2.`. 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`. | |
``` |
@noklam I think this is clearer?
I've actually always thought (and I think @Galileo-Galilei agrees) that we should change this behaviour since in reality no one maintains a starters repo which they keep up to date with every single version of the kedro template.
- by default don't try and checkout the kedro version unless it's an official starter (cookiecutter will by default look for the right
main
/master
branch if you don't specifycheckout
) - and/or enable people to specify
checkout
in theirKedroStarterSpec
But that's a discussion for another time.
I think we should do the change from Edit: actually the e2e test isn't urgent tbh... I just thought it would be easiest to stick it in this PR also given the e2e test change is already here. |
Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com>
Signed-off-by: Nok Chan <nok.lam.chan@quantumblack.com>
…ase/0.18.2 Signed-off-by: Nok Chan <nok.lam.chan@quantumblack.com>
Signed-off-by: Nok Chan <nok.lam.chan@quantumblack.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Nok Chan <nok.lam.chan@quantumblack.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Ahdra Merali <ahdra.merali@quantumblack.com>
Description
Release 0.18.2
Major features and improvements
abfss
to list of cloud protocols, enabling abfss paths.conf/base/logging.yml
is now optional. See our documentation for details.kedro.starters
entry point. This enables plugins to create custom starter aliases used bykedro starter list
andkedro new
.kedro new
prompts to just one question asking for the project name.Bug fixes and other changes
pyyaml
upper bound to make Kedro compatible with the pyodide stack.myst_parser
instead ofrecommonmark
.INFO
toDEBUG
for low priority messages.info.log
/errors.log
files are no longer created in your project root, and running Kedro on read-only file systems such as Databricks Repos is now possible.root
logger is now set to the Python default level ofWARNING
rather thanINFO
. Kedro's logger is still set to emitINFO
level messages.SequentialRunner
now has consistent execution order across multiple runs with sorted nodes.kedro jupyter notebook/lab
no longer reuses a Jupyter kernel.cookiecutter>=2.1.1
to address a known command injection vulnerability.getpass.getuser
.AbstractDataSet
andAbstractVersionedDataSet
as well as typing to all datasets.Minor breaking changes to the API
kedro.config.default_logger
no longer exists; default logging configuration is now set automatically throughkedro.framework.project.LOGGING
. Unless you explicitly importkedro.config.default_logger
you do not need to make any changes.Upcoming deprecations for Kedro 0.19.0
kedro.extras.ColorHandler
will be removed in 0.19.0.Checklist
RELEASE.md
file