As well as downloading the latest muse2 release for each OS in the CI and testing against them to make sure the notebooks still work, we also want to build the current main branch of muse2 and test against each build. We can likely follow a similar recipe to the muse2 ci script but doing seperate checkouts for the data analysis repo and the muse2 one.
Probably don't need to run cargo test because that should always be passing in main anyway?
As well as downloading the latest muse2 release for each OS in the CI and testing against them to make sure the notebooks still work, we also want to build the current main branch of muse2 and test against each build. We can likely follow a similar recipe to the muse2 ci script but doing seperate checkouts for the data analysis repo and the muse2 one.
Probably don't need to run
cargo testbecause that should always be passing inmainanyway?