Juan Luis Cano Rodríguez

Glad you asked 😄 The same redirection trick can be applied in `kedro-datasets`, which will _finally_ bring consistency among all subprojects.

`/en/latest` is now a HTTP 301 redirection to `/en/unreleased` in all 3 projects ✔

`/en/stable` is now a HTTP 302 dynamic redirection to the most recent released version in all 3 projects ✔

Hi all, we've carefully considered this and we decided to do another 0.19 release, but after we have released 1.0. Please stay tuned and thanks for your patience!

@g199209 We're working with downstream plugin authors, and specifically with kedro-mlflow, to make 1.0 compatibility a reality soon 🙏🏼

(It seems like I'm solutionising here, please don't take it as such - it's more of a brain dump after an exceedingly long yak shaving session)

Earlier, related, idea at kedro-org/kedro-viz#1857.

Yeah it's connected to the deployment piece in a sense! Moving this here for visibility since it's mostly a Kedro "core" workstream.

Today a user asked how to access the pipeline definition "outside the normal `kedro run` life cycle" with this use case in mind: > generate documentation via a mermaid diagram...

Recently we've found an instance of Kedro-Viz yielding an error when `kedro run` was working and it's not even clear how to debug that without seeing the actual code. https://kedro.hall.community/kedro-viz-errors-zqfc1XFylfpd...