v0.7.0 : more thorough checking and covering of pit falls
Updating denv check to help it be more usable by a wider audience and give more information to the user is a good step towards stability. More testing on non-normal systems (e.g. NixOS and clusters with multiple runners) revealed some other pit-falls that can be avoided.
💥 Breaking Change
#96 and #98 re-order the list of runners that denv checks when trying to deduce which runner to use at start-up if DENV_RUNNER is not defined. This means that on systems with multiple runners available, the runner chosen to be used by denv may change which may cause some discomfort if not breaking a setup. Both of the order changes were motivated by usability: promoting runners that are more likely to be usable for denv (in my experience). All in all, I'd recommend to define DENV_RUNNER in your host environment if you have multiple runners installed. I've added this recommendation to the manual pages as well.
What's Changed
- enter the workspace whether or not it needs creation by @tomeichlersmith in #91
- update
denv checkwith emulation testing and workspace search by @tomeichlersmith in #96 - re-order runner deduction to prefer apptainer/singularity by @tomeichlersmith in #98
🤖 bot changes 🤖
- Auto Runner Version Update by @github-actions in #89
- Auto Runner Version Update by @github-actions in #90
- Auto Runner Version Update by @github-actions in #95
- Auto Man Page Update by @github-actions in #97
- Auto Man Page Update by @github-actions in #99
- Auto Man Page Update by @github-actions in #100
We've reached 💯 PRs and Issues 🎉
Full Changelog: v0.6.0...v0.7.0
