Experiment: Use release profile for CI tests

[maackle]

Summary

We were using a dev profile for building workspace crates, and a release-ish profile for all other deps. Let's see what it looks like to use release for everything.

TODO:

• CHANGELOGs updated with appropriate info

[ThetaSinner]

Looks like we have a test depending on being in debug mode? :D

Otherwise though this looks to me like it should work, based on a read through the holochain.nix module which uses this. Seems like a good idea unless there was another reason to have test deps build in debug mode

[maackle]

Yes, due to an expectation of debug_assert! causing a panic. I think our use of debug_assert is appropriate and should be included in CI. I enabled debug in the profile for workspace deps so let's see how that looks in the CI run.

[maackle]

The CI process consistently gets killed during compilation. My guess is the runner just can't/won't handle the load. We could loop back on this some time, but I'm going to consider the experiment concluded for now. Let's let stalebot close this.

[github-actions]

This item has been open for 30 days with no activity.

[github-actions]

This item has been inactive for 14 days since being marked as stale.