Closed jmoalves closed 3 years ago
The Levain upgrade is not that easy... We have a running Deno that needs an upgrade as well.
When we try to save the previous version, the "SAVE-DEL" activity encounters an error. This happens because the deno.exe is opened.
Perhaps the best way to implement this is to have a "bootstrap" class that checks for upgrades and perform the upgrade before loading levain.
Perhaps we should start a new shell with the new Levain version
Another approach is to stop treating levain as a regular recipe. Perhaps we should keep it in another directory. Or we could always use the levain bootstrap to load levain.
Release 0.35.0+ solves this
Depends on #6.
We should monitor the
releases
at GitHub and use the latest release as another repository, upfront in the repository chain.We will create another problem... How do we use the new Levain version to run the upgrade? I believe we can live with that :-)