arek-kwapis
commented
1 year ago This is actually a very good point! Once we come closer to release and have tangible builds of RustedAnvil, the plan is to change over from commit-based to release-based.
If you look around on the master and 1.6.4_965 branches, you'll find a currently empty "Releases" section. Releases are either commits up to that point packaged into a zip or the commit up to that point compiled into an output.
Take a look at this repository as a good example of how RustedAnvil may look in the future regarding releases: spicetify-cli repository
Notice how there is a release from 2 weeks ago with a full changelog since last release and a list of downloads for each platform (the zips contain the executables and any required files), meanwhile there have been commits as recently as 4 days ago. Once enough commits happen with changes, a new release is made with a changelog and the compiled code from all the commits up to that point. That's what we will be doing with RustedAnvil as well.
Hopefully that clears it up a bit!
Is your feature request related to a problem? Please describe. The updates are for now commit-based and it causes problems about upgrading / downgrading versions.
Describe the solution you'd like A release-based update system with respective labels {i.e. 0.6.7, 1.3.5} and a changelog {added x, removed y etc.}
Describe alternatives you've considered Backups of old versions of RustedAnvil
Additional context This system would make the updates more organised and if an update was problematic, this would allow downgrading to version before the problematic update.