Run pixi lockfile regeneration more often (every Monday at 5am UTC)

[valeriupredoi]

Description

I had this as a bit of a pet peeve since we implemented pixi functionality ie we ought to update the lockfiles more often that just once a month, but now I've seen the need of it with OSX env breaking pretty often. I reckon once a week is just fine.

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🛠 This pull request has a descriptive title
• 🛠 Any changed dependencies have been added or removed correctly
• 🛠 All checks below this pull request were successful

[valeriupredoi]

agh looks like I need to clean up my local GH repo, it's full of unstashed refs - meh, should be OK here or you want me to close and reopen after I've cleaned it?

[bouweandela]

I think we need to test better before merging the updated lockfile to prevent breaking the environment instead of updating more often. The advantage of not updating too often is that you don't need to install a new environment so often.

[valeriupredoi]

I think we need to test better before merging the updated lockfile to prevent breaking the environment instead of updating more often. The advantage of not updating too often is that you don't need to install a new environment so often.

I don't think we can detect such issues with better testing: a PR is not always responsible for breaking the env; it's the new deps that get released after it was merged that break the pip check - in fairness, I am not even sure why the whole show breaks, let me get my head around it and understand why that pip check fails, and if indeed recreating the lock file more often is a solution - am putting this into a Draft for now