lix-project/lix-website
3
1
Fork 14
Code Issues 3 Pull requests 5 Packages Projects Releases Wiki Activity

doc: update tag and version from 2.90-beta1 to 2.90.0-rc1 #29

Merged
jade merged 2 commits from drupol/lix-website:lix-bump-tag-june-2024 into main 2024-06-20 06:54:19 +00:00
Conversation 0 Commits 2 Files changed 2 +22 -22
2 changed files with 22 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 92b9c4408b - Show all commits

8
content/add-to-config.md
View file

@ -23,7 +23,7 @@ Adding Lix to a flake-based configuration is relatively simple. First, add the L
# which is often the case. If you've named it something else,
# you'll need to change the `nixpkgs` below.
lix = {
url = "git+https://git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.1";
url = "git+https://git.lix.systems/lix-project/lix?ref=refs/tags/2.90.0-rc1";
jade commented 2024-06-19 22:46:47 +00:00
Outdated
Review
Copy link

please also update lix-nixos-module to tag 2.90.0-rc1 :) we had to actually make this follow tags now that we have two branches.

please also update lix-nixos-module to tag 2.90.0-rc1 :) we had to actually make this follow tags now that we have two branches.
flake = false;
};
lix-module = {
@ -98,7 +98,7 @@ You should now be using Lix! You can verify this by asking the `nix` command to
```sh
$ nix --version
nix (Lix, like Nix) 2.90.0-beta.1
nix (Lix, like Nix) 2.90.0-rc1-lixpre20240615-253546d
```
As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
@ -138,7 +138,7 @@ section, and add the line provided in the configuration
(fetchTarball { url = "https://git.lix.systems/lix-project/nixos-module/archive/main.tar.gz"; }) + "/module.nix"
)
{
lix = fetchTarball { url = "https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz"; };
lix = fetchTarball { url = "https://git.lix.systems/lix-project/lix/archive/2.90.0-rc1.tar.gz"; };
}
)
];
@ -167,7 +167,7 @@ You should now be using Lix! You can verify this by asking the `nix` command to
```sh
$ nix --version
nix (Lix, like Nix) 2.90.0-beta.1
nix (Lix, like Nix) 2.90.0-rc1-lixpre20240615-253546d
```
As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a

4
content/install.md
View file

@ -72,7 +72,7 @@ Thanks to Nix, we can actually ask Lix to upgrade your system directly. Run the
sudo --preserve-env=PATH nix run \
--experimental-features "nix-command flakes" \
--extra-substituters https://cache.lix.systems --extra-trusted-public-keys "cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o=" \
'git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.1' -- \
'git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90.0-rc1' -- \
upgrade-nix \
--extra-substituters https://cache.lix.systems --extra-trusted-public-keys "cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o="
```
@ -82,7 +82,7 @@ to report its version:
```sh
$ nix --version
nix (Lix, like Nix) 2.90.0-beta.1
nix (Lix, like Nix) 2.90.0-rc1-lixpre20240615-253546d
```
As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a