Skip to content

Releases: DeterminateSystems/nix-installer

v0.5.0

06 Mar 20:20
9d939e7
Compare
Choose a tag to compare

This release includes some more work towards supporting installing over existing installations (see #126 for more information on our curing effort). Specifically, an existing /etc/nix/nix.conf file will no longer be a hard error1 and will instead be merged with the settings that we desire.

It also fixes a few bugs, like a typo in a permissions check (checking a file had a mode of 664 instead of 644), a macOS installation bug that affected some setups (see #295 and #298 for more information), and explicitly erroring on WSL1 as unsupported.

If you rely on us as a library, the change that will impact you the most is that we made all of our error enums #[non_exhaustive], so that adding new variants in the future won't require a new major version.

The diagnostics report also saw a slight rework to be somewhat more useful in actually diagnosing issues. A diagnostic report now looks like this:

{
  "version": "0.5.0",
  "planner": "linux",
  "configured_settings": [
    "modify_profile"
  ],
  "os_name": "Ubuntu",
  "os_version": "22.04.1 LTS (Jammy Jellyfish)",
  "triple": "x86_64-unknown-linux-musl",
  "is_ci": false,
  "action": "Install",
  "status": "Failure",
  "failure_chain": [
    "Action(\"configure_nix\")",
    "Child(\"place_nix_configuration\")",
    "Child(\"create_directory\")",
    "CreateDirectory(\"/etc/nix\")"
  ]
}

What's Changed

Full Changelog: v0.4.0...v0.5.0


  1. Currently, only experimental-features will be merged (please file an issue if you would like to see other options supported!); any other conflict between our desired settings and an existing nix.conf will still cause an error. In other words, if the setting is not one that we are trying to set (see the list here: https://github.com/DeterminateSystems/nix-installer/blob/v0.5.0/src/action/common/place_nix_configuration.rs#L32-L45), it will be seamlessly merged into the resulting nix.conf file.

v0.4.0

24 Feb 23:03
f9f9278
Compare
Choose a tag to compare

With 0.4.0, we're feeling like the Determinate Nix Installer is ready for general usage.

It's pretty exciting and we invite you to enjoy a cupcake to celebrate with us! 🧁

As part of this step up in stability, we managed to re-enable deleting users on Macs. We originally disabled this feature because our test Macs were giving strange errors. Turns out, it's because we weren't logged in graphically, so even though our user had a secure token, they still couldn't remove users! For more details, check out #33.

We also got feedback from some users (thanks!) that the permission mode checking we added last version was too strict and in some places just plain wrong. Those should be fixed up and the errors related to them greatly improved.

This release also includes a diagnostic reporting tool, allowing adopters to report back the status of installs. This is handy if you're deploying Nix across an organization and want to catch problems with deployments. The reporter is configurable and can write small reports to files or URLs that look like this:

{
    "version": "0.4.0",
    "planner": "linux",
    "configured_settings": [ "modify_profile" ],
    "os_name": "Ubuntu",
    "os_version": "22.04.1 LTS (Jammy Jellyfish)",
    "triple": "x86_64-unknown-linux-gnu",
    "action": "Install",
    "status": "Failure",
    "failure_variant": "Symlink"
}

If your organization starts using them, please let us know! We'd like to know more about how to make them useful. The default options of the installer drop a diagnostic to us to help us root out problems. Diagnostic reporting can always be disabled by adding --diagnostic-endpoint= to the end of the install command.

We also fixed an issue with nix-shell -p not working when it should have! We now add extra-nix-path = nixpkgs=flake:nixpkgs to the nix.conf.

Lastly, this release includes a number of minor "curing" functionality, meaning things like a /nix folder already existing won't immediately cause an error. These items will still cleanly get removed on uninstall. It's intended that this functionality helps repair existing partial installs (from any source).

What's Next

Next release we plan to focus more on "curing". It's our hope we can offer users the ability to repair existing installs, complete previous partial install attempts, and offer users a chance to uninstall an existing (non nix-installer created) install. As part of that we've been hacking on nix-config-parser and it's been a lot of fun!

What's Changed

Full Changelog: v0.3.0...v0.4.0

v0.3.0

14 Feb 18:11
41fdc2d
Compare
Choose a tag to compare

This release includes some fixes for issues users were experiencing on the Steam Deck, as well as some improved error messages. Several actions can now recognize existing partial installs and transparently take ownership of them.

We decided on the phrasing "The Determinate Nix Installer" when regarding this project and not wanting to use the binary name. We also adopted an increased software maturity stance.

We also noted that the planners felt awkwardly named given that linux-multi was able to install the root only mode. We renamed them from linux-multi to linux, and darwin-multi to macos. (steam-deck is unchanged) You may need to adjust your scripts to compensate for this.

Bug fixes

  • Attempt to minimize steam deck display manager restart risk by @Hoverbear in #237

What's Changed

Full Changelog: v0.2.0...v0.3.0

v0.2.0

01 Feb 22:10
95852f2
Compare
Choose a tag to compare

This release includes some fixes users reported on Macs (notably #212) and introduces a new init-less option for Linux.

Using --init none lets users enjoy Nix in places where an init system is not present. Since the darwin-multi and the steam-deck planners require the init system for mounting /nix, they did not receive a similar option. --init none permits use cases such as WSL2 (without Systemd) or inside running Docker containers.

Users of the linux-multi planner can also try --no-start-daemon which allows for Nix to be installed during a docker build command.

Bugfixes

  • Use a UUID instead of volume name for fstab on Mac by @Hoverbear in #215

What's Changed

  • Add a friendly top comment about nix-installer.sh by @Hoverbear in #216
  • Verify the apfs volume doesn't already exist before trying to create it by @Hoverbear in #217
  • Add plist use to the CreateFstabEntry action by @Hoverbear in #221
  • Use 30k range not 3k range for UIDs on Linux and 30k for a GID on all by @Hoverbear in #222
  • init-less install by @Hoverbear in #188

Full Changelog: v0.1.0...v0.2.0

v0.1.0

20 Jan 22:59
501d7ee
Compare
Choose a tag to compare

We opted to cut a 0.1.0 for a marker of maturity more than a version breakage.

There was a minor API change if you were using the NIX_INSTALLER_NO_MODIFY_PROFILE env as it got renamed to NIX_INSTALLER_MODIFY_PROFILE.

What's Changed

Full Changelog: v0.0.2...v0.1.0

v0.0.2

19 Jan 21:58
24a94ec
Compare
Choose a tag to compare

Since v0.0.1 we moved our Github Action to https://github.com/DeterminateSystems/nix-installer-action. If you were using the action from this repository previously, please use the new one. This change was #185.

Bugfixes

What's Changed

Full Changelog: v0.0.1...v0.0.2

v0.0.1

09 Jan 22:11
bbeed6a
Compare
Choose a tag to compare

An initial release of nix-installer.

This is mostly for testing our release process, a 0.1.0 will be the first announced release.

Milestone: https://github.com/DeterminateSystems/nix-installer/milestone/2?closed=1