Hey @drumtorben thanks for this PR.
Are you able to run all the pipelines in your local with this branch? I couldn't, I had to fix the dependencies I had on the poetry lock to the uv lock to make it work.

have you tested all automations? inv formats etc..?

I'm not sure Im using uv correctly :P maybe I missed something. Once I get all pipelines working on this branch we can merge it!

Both is working for me. I get the MLFlow error in the end, but that was the same for me before the switch.

Yeah, from the screenshot it could probably be that you are in the wrong environment or so? I am not completely sure about that ...

EDIT: Fixed the MLFlow error by setting AWS_ACCESS_KEY_ID, AWS_REGION, and AWS_SECRET_ACCESS_KEY in the .env to dummy values. I now get a connection error, but this is of course due to the dummy values, as I have no AWS instances running.

One thing I was just thinking about:
Did you delete your .venv folder, which was created by poetry? If not, delete it and then run uv sync —all-groups. This creates then a new .venv folder.

If you are in VSCode you now should be asked about using this environment, else you have to activate it manually with source .venv/bin/activate.