diff --git a/index.xhtml b/index.xhtml index 468320cf1..49fd8aeb8 100644 --- a/index.xhtml +++ b/index.xhtml @@ -29,7 +29,7 @@

Home Manager Manual

-

Version 26.05 (unstable)

+

Version 26.05

@@ -85,7 +85,7 @@ Nix option. On NixOS you can control this option using the system option.

  • Add the appropriate Home Manager channel. If you are following Nixpkgs master or an unstable channel you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
 $ nix-channel --update
-

    and if you follow a Nixpkgs version 25.11 channel you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-25.11.tar.gz home-manager
+

    and if you follow a Nixpkgs version 26.05 channel you can run

    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-26.05.tar.gz home-manager
 $ nix-channel --update

  • Run the Home Manager installation command and create the first Home Manager generation:

    $ nix-shell '<home-manager>' -A install
@@ -114,7 +114,7 @@ your system configuration. This is most conveniently done by adding a
 Home Manager channel to the root user. For example, if you are following
 Nixpkgs master or an unstable channel, you can run
    $ sudo nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
 $ sudo nix-channel --update
-
    and if you follow a Nixpkgs version 25.11 channel, you can run
    $ sudo nix-channel --add https://github.com/nix-community/home-manager/archive/release-25.11.tar.gz home-manager
+
    and if you follow a Nixpkgs version 26.05 channel, you can run
    $ sudo nix-channel --add https://github.com/nix-community/home-manager/archive/release-26.05.tar.gz home-manager
 $ sudo nix-channel --update
 
    It is then possible to add
    imports = [ <home-manager/nixos> ];
 
    to your system configuration.nix file, which will introduce a new
@@ -122,7 +122,7 @@ NixOS option called home-manager.users whose type i
 that maps user names to Home Manager configurations.
    Alternatively, home-manager installation can be done declaratively through configuration.nix using the following syntax:
    { config, pkgs, lib, ... }:
 
 let
-  home-manager = builtins.fetchTarball https://github.com/nix-community/home-manager/archive/release-25.11.tar.gz;
+  home-manager = builtins.fetchTarball https://github.com/nix-community/home-manager/archive/release-26.05.tar.gz;
 in
 {
   imports =
@@ -137,7 +137,7 @@ in
 
     # The state version is required and should stay at the version you
     # originally installed.
-    home.stateVersion = "25.11";
+    home.stateVersion = "26.05";
   };
 }
 
    For example, a NixOS configuration may include the lines
    users.users.eve.isNormalUser = true;
@@ -152,7 +152,7 @@ home-manager.users.eve = { pkgs, ... }: {
   # You should not change this value, even if you update Home Manager. If you do
   # want to update the value, then make sure to first check the Home Manager
   # release notes.
-  home.stateVersion = "25.11"; # Please read the comment before changing. 
+  home.stateVersion = "26.05"; # Please read the comment before changing.
 
 };
 
    and after a sudo nixos-rebuild switch the user eve’s environment
@@ -192,7 +192,7 @@ into your system configuration. This is most conveniently done by adding
 a Home Manager channel. For example, if you are following Nixpkgs master
 or an unstable channel, you can run
    $ nix-channel --add https://github.com/nix-community/home-manager/archive/master.tar.gz home-manager
 $ nix-channel --update
-
    and if you follow a Nixpkgs version 25.11 channel, you can run
    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-25.11.tar.gz home-manager
+
    and if you follow a Nixpkgs version 26.05 channel, you can run
    $ nix-channel --add https://github.com/nix-community/home-manager/archive/release-26.05.tar.gz home-manager
 $ nix-channel --update
 
    It is then possible to add
    imports = [ <home-manager/nix-darwin> ];
 
    to your nix-darwin configuration.nix file, which will introduce a
@@ -207,7 +207,7 @@ home-manager.users.eve = { pkgs, ... }: {
 
   # The state version is required and should stay at the version you
   # originally installed.
-  home.stateVersion = "25.11";
+  home.stateVersion = "26.05";
 };

    and after a darwin-rebuild switch the user eve’s environment should include a basic Bash configuration and the packages atool and httpie.

    If you do not plan on having Home Manager manage your shell @@ -279,7 +279,7 @@ command performs a combined build and activation.

    { config, pkgs, ... }:
   # You can update Home Manager without changing this value. See
   # the Home Manager release notes for a list of state version
   # changes in each release.
-  home.stateVersion = "25.11";
+  home.stateVersion = "26.05";
 
   # Let Home Manager install and manage itself.
   programs.home-manager.enable = true;
@@ -847,7 +847,7 @@ introduction about writing a Home Manager configuration.
    • user, you can run the Home Manager init command directly from its flake.

    For example, if you are using the unstable version of Nixpkgs or NixOS, then to generate and activate a basic configuration run the command

    $ nix run home-manager/master -- init --switch
-

    For Nixpkgs or NixOS version 25.11 run

    $ nix run home-manager/release-25.11 -- init --switch
+

    For Nixpkgs or NixOS version 26.05 run

    $ nix run home-manager/release-26.05 -- init --switch

    This will generate a flake.nix and a home.nix file in ~/.config/home-manager, creating the directory if it does not exist.

    If you need to pass additional values from your flake to home.nix or any imported Home Manager modules, use extraSpecialArgs in the call to @@ -874,7 +874,7 @@ This is useful if you want to inspect and edit the configuration before activating it.

    $ nix run home-manager/$branch -- init
 $ # Edit files in ~/.config/home-manager
 $ nix run home-manager/$branch -- init --switch
-

    Where $branch is one of master or release-25.11.

    After the initial activation has completed successfully then building +

    Where $branch is one of master or release-26.05.

    After the initial activation has completed successfully then building and activating your flake-based configuration is as simple as

    $ home-manager switch

    It is possible to override the default configuration directory, if you want. For example,

    $ nix run home-manager/$branch -- init --switch ~/hmconf
diff --git a/release-notes.xhtml b/release-notes.xhtml
index e8e786eb7..5de356c7a 100644
--- a/release-notes.xhtml
+++ b/release-notes.xhtml
@@ -25,8 +25,7 @@
    
    
    
   
     
      
       
        
    Appendix D. Release Notes   
      
     
     
    Table of Contents
     
      
       Release 26.05 
       Release 25.11 
       Release 25.05 
       Release 24.11 
       Release 24.05 
       Release 23.11 
       Release 23.05 
       Release 22.11 
       Release 22.05 
       Release 21.11 
       Release 21.05 
       Release 20.09 
       Release 20.03 
       Release 19.09 
       Release 19.03 
       Release 18.09 
     
    This section lists the release notes for stable versions of Home Manager
-and the current unstable version.
     
      
       
        
    Release 26.05   
      
     
     
    Table of Contents
     
      
       Highlights 
       State Version Changes 
     
    This is the current unstable branch and the information in this
-section is therefore not final.
     
      
       
        
    Highlights   
      
     
    This release has the following notable changes:
    • WezTerm now supports declarative configuration via
+and the current unstable version.
       
        
         
          
      Release 26.05   
        
       
       
      Table of Contents
       
        
         Highlights 
         State Version Changes 
       
      The 26.05 release branch became stable in May, 2026.
       
        
         
          
      Highlights   
        
       
      This release has the following notable changes:
      • WezTerm now supports declarative configuration via
 programs.wezterm.settings. Settings are expressed as a Nix
 attribute set and serialized to Lua using lib.generators.toLua.
 Raw Lua expressions such as wezterm.font and wezterm.action.*