Skip to content

Releases: rollingrhinoremix/rhino-config

v3.1.0

20 Jul 14:32
468941b
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.0...v3.1.0

rhino-config v3.0 - Kernel Switching

10 Jun 21:18
e87c0f9
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.0.1...v3.0

Release notes: https://rollingrhino.org/blog#rhino-config-v300

rhino-config v2.0.1 - Bug fixes

02 May 16:23
4329368
Compare
Choose a tag to compare

What's Changed

  • refactor: use anyhow
  • fix: enable -s, disable -p, disable -s subcommands

Full Changelog: v2.0...v2.0.1

rhino-config v2.0 - Convert rhino-config into a CLI Utility

26 Apr 20:00
e661d8c
Compare
Choose a tag to compare

After a few weeks of development, we are officially ready to release rhino-config v2.0! A large thank you to our core maintainer @wizard-28 who has completely re-written the utility in Rust. The upgraded utility is no-longer a bash alias that will download a script, but a command-line utility which will be upgraded via our rhino-upgrade script.

You can read more about it here: https://rollingrhino.org/blog#config-v2

rhino-config v1.2 - Pacstall integration

20 Apr 11:50
3b5e8a2
Compare
Choose a tag to compare

We have integrated, along with the help of the Pacstall development team, Pacstall directly into our Rhino utilities. Pacstall can now be enabled via rhino-config and all Pacstall applications can be updated via rhino-update.

rhino-config has also received some new features, such as the user not being prompted multiple times for configurations that they have already enabled.

rhino-config v1.1 - Code Refactor

19 Apr 15:40
ec572de
Compare
Choose a tag to compare

The code for rhino-config has been refactored by our new rhino-config maintainer @wizard-28 - The script now follows better programming standards as a result of this. It now also has error handling. Other than that, not much has changed.

1.0 - First tagged release

16 Apr 11:48
566254a
Compare
Choose a tag to compare

With both rhino-config and rhino-update being updated irrespective of the distribution following the next release, we have decided to tag both of these releases. We are using the semver versioning scheme. Both versions will begin at v1.0 despite being used in production before. This is due to the fact they have been given some features which make the software more useful as opposed to utilizing apt.