feat: upgrade to 25.11 (#266)

Author: ryan4yin

docs/en/best-practices/remote-deployment.md

@@ -92,7 +92,7 @@ below:
 ```nix{11-34}
 {
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
 
     # ...
   };

docs/en/development/cross-platform-compilation.md

@@ -79,15 +79,15 @@ need to add a Module in `flake.nix`, as shown below:
   description = "NixOS running on LicheePi 4A";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
   };
 
   outputs = inputs@{ self, nixpkgs, ... }: {
     nixosConfigurations.lp4a = nixpkgs.lib.nixosSystem {
       modules = [
         {
           # the platform that performs the build-step
-          nixpkgs.localSystem.system = "x86_64-linux"; 
+          nixpkgs.localSystem.system = "x86_64-linux";
 
           # the platform that will execute the resulting binaries
           # add this to enable cross-compilation.
@@ -134,7 +134,7 @@ cross-compilation, as shown below:
   description = "NixOS running on LicheePi 4A";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
   };
 
   outputs = inputs@{ self, nixpkgs, ... }: {
@@ -150,10 +150,10 @@ cross-compilation, as shown below:
 }
 ```
 
-You do not need to add any additional modules, just specify `nixpkgs.hostPlatform` as `riscv64-linux`.
-Nix will automatically detect whether the current system is `riscv64-linux` during the
-build. If not, it will automatically build through the emulated system(QEMU). For users,
-these underlying operations are completely transparent.
+You do not need to add any additional modules, just specify `nixpkgs.hostPlatform` as
+`riscv64-linux`. Nix will automatically detect whether the current system is
+`riscv64-linux` during the build. If not, it will automatically build through the emulated
+system(QEMU). For users, these underlying operations are completely transparent.
 
 ## Linux binfmt_misc
 
@@ -240,7 +240,7 @@ So how to use this method in Flakes? The example `flake.nix` is as follows:
   description = "NixOS running on LicheePi 4A";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05-small";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11-small";
   };
 
   outputs = { self, nixpkgs, ... }:
@@ -249,7 +249,7 @@ So how to use this method in Flakes? The example `flake.nix` is as follows:
       modules = [
         {
           # the platform that performs the build-step
-          nixpkgs.localSystem.system = "x86_64-linux"; 
+          nixpkgs.localSystem.system = "x86_64-linux";
 
           # the platform that will execute the resulting binaries
           # add this to enable cross-compilation.
@@ -279,7 +279,7 @@ follows:
   description = "NixOS running on LicheePi 4A";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05-small";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11-small";
   };
 
   outputs = { self, nixpkgs, ... }: let
@@ -300,7 +300,7 @@ follows:
       };
       modules = [
         {
-          nixpkgs.localSystem.system = "x86_64-linux"; 
+          nixpkgs.localSystem.system = "x86_64-linux";
           nixpkgs.crossSystem.system = "riscv64-linux";
         }
 

docs/en/development/intro.md

@@ -115,7 +115,7 @@ Here is a `flake.nix` that defines a development environment with Node.js 24 ins
   description = "A Nix-flake-based Node.js development environment";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
   };
 
   outputs = { self , nixpkgs ,... }: let
@@ -156,7 +156,7 @@ Here is an example:
   description = "A Nix-flake-based Node.js development environment";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
   };
 
   outputs = { self , nixpkgs ,... }: let
@@ -204,7 +204,7 @@ Example:
   description = "A Nix-flake-based Node.js development environment";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
   };
 
   outputs = { self , nixpkgs ,... }: let
@@ -275,7 +275,7 @@ the `dev-shell` command, which is the special feature of `pkgs.runCommand` compa
 Related source code:
 
 - [pkgs/build-support/trivial-builders/default.nix - runCommand](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/pkgs/build-support/trivial-builders/default.nix#L21-L49)
-- [pkgs/build-support/setup-hooks/make-wrapper.sh](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/pkgs/build-support/setup-hooks/make-wrapper.sh)
+- [pkgs/build-support/setup-hooks/make-wrapper.sh](https://github.com/NixOS/nixpkgs/blob/nixos-25.11/pkgs/build-support/setup-hooks/make-wrapper.sh)
 
 ## Enter the build environment of any Nix package
 

docs/en/development/kernel-development.md

@@ -9,7 +9,7 @@ An example of kernel development with `flake.nix`.
   description = "NixOS running on LicheePi 4A";
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05-small";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11-small";
 
     # custom kernel's source
     thead-kernel = {

docs/en/development/packaging-101.md

@@ -17,9 +17,9 @@ packaging.
     with hash prefetching, dependency inference, license detection, and more
 - Source Code:
   - [pkgs/build-support/trivial-builders/default.nix - runCommand](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/pkgs/build-support/trivial-builders/default.nix#L21-L49)
-  - [pkgs/build-support/setup-hooks/make-wrapper.sh](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/pkgs/build-support/setup-hooks/make-wrapper.sh)
+  - [pkgs/build-support/setup-hooks/make-wrapper.sh](https://github.com/NixOS/nixpkgs/blob/nixos-25.11/pkgs/build-support/setup-hooks/make-wrapper.sh)
   - FHS related
-    - [pkgs/build-support/build-fhsenv-bubblewrap/buildFHSEnv.nix](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/pkgs/build-support/build-fhsenv-bubblewrap/buildFHSEnv.nix):
+    - [pkgs/build-support/build-fhsenv-bubblewrap/buildFHSEnv.nix](https://github.com/NixOS/nixpkgs/blob/nixos-25.11/pkgs/build-support/build-fhsenv-bubblewrap/buildFHSEnv.nix):
       `pkgs.buildFHSEnvBubblewrap`
-    - [pkgs/build-support/build-fhsenv-chroot/default.nix](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/pkgs/build-support/build-fhsenv-bubblewrap/buildFHSEnv.nix):
+    - [pkgs/build-support/build-fhsenv-chroot/default.nix](https://github.com/NixOS/nixpkgs/blob/nixos-25.11/pkgs/build-support/build-fhsenv-bubblewrap/buildFHSEnv.nix):
       `pkgs.buildFHSEnvChroot`

docs/en/nix-store/add-binary-cache-servers.md

@@ -139,7 +139,7 @@ The second method is to configure `substituters` and `trusted-public-keys` using
   };
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
 
     # omitting several configurations...
   };
@@ -226,7 +226,7 @@ In other words, you can use it like this:
   };
 
   inputs = {
-    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
 
     # omitting several configurations...
   };

docs/en/nixos-with-flakes/downgrade-or-upgrade-packages.md

@@ -17,8 +17,8 @@ commit or branch:
     nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
 
     # Latest stable branch of nixpkgs, used for version rollback
-    # The current latest version is 25.05
-    nixpkgs-stable.url = "github:nixos/nixpkgs/nixos-25.05";
+    # The current latest version is 25.11
+    nixpkgs-stable.url = "github:nixos/nixpkgs/nixos-25.11";
 
     # You can also use a specific git commit hash to lock the version
     nixpkgs-fd40cef8d.url = "github:nixos/nixpkgs/fd40cef8d797670e203a27a91e4b8e6decf0b90c";

docs/en/nixos-with-flakes/modularize-the-configuration.md

@@ -284,7 +284,7 @@ project:
 ```nix{8-36}
 # flake.nix
 {
-  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
   outputs = {nixpkgs, ...}: {
     nixosConfigurations = {
       "my-nixos" = nixpkgs.lib.nixosSystem {
@@ -331,7 +331,7 @@ strings, single-line strings, and lists. Let's test the results:
 ```bash
 # Example 1: multiline string merging
 › echo $(nix eval .#nixosConfigurations.my-nixos.config.programs.bash.shellInit)
-trace: warning: system.stateVersion is not set, defaulting to 25.05. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersio
+trace: warning: system.stateVersion is not set, defaulting to 25.11. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersio
 n.
 "echo 'insert before default'
 
@@ -368,4 +368,4 @@ order of definition.
 ## References
 
 - [Nix modules: Improving Nix's discoverability and usability](https://cfp.nixcon.org/nixcon2020/talk/K89WJY/)
-- [Module System - Nixpkgs](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/doc/module-system/module-system.chapter.md)
+- [Module System - Nixpkgs](https://github.com/NixOS/nixpkgs/blob/nixos-25.11/doc/module-system/module-system.chapter.md)

docs/en/nixos-with-flakes/nixos-flake-and-module-system.md

@@ -59,7 +59,7 @@ automatically injected, and declaration-free parameters** provided by the module
      (e.g. `x86_64-linux`), and the value of `pkgs` can be customized through the
      `nixpkgs.pkgs` option.
 5. `modulesPath`: A parameter available only in NixOS, which is a path pointing to
-   [nixpkgs/nixos/modules](https://github.com/NixOS/nixpkgs/tree/nixos-25.05/nixos/modules).
+   [nixpkgs/nixos/modules](https://github.com/NixOS/nixpkgs/tree/nixos-25.11/nixos/modules).
    - It is defined in
      [nixpkgs/nixos/lib/eval-config-minimal.nix#L43](https://github.com/NixOS/nixpkgs/blob/nixos-25.05/nixos/lib/eval-config-minimal.nix#L43).
    - It is typically used to import additional NixOS modules and can be found in most
@@ -86,7 +86,7 @@ to understand. If readers are interested, I will include the links here:
 1. `_module.args`:
    - NixOS Manual:
      [Appendix A. Configuration Options](https://nixos.org/manual/nixos/stable/options#opt-_module.args)
-   - Source Code: [nixpkgs/nixos-25.05/lib/modules.nix - _module.args]
+   - Source Code: [nixpkgs/nixos-25.11/lib/modules.nix - _module.args]
 
 In short, `specialArgs` and `_module.args` both require an attribute set as their value,
 and they serve the same purpose, passing all parameters in the attribute set to all
@@ -110,7 +110,7 @@ Suppose you want to pass a certain dependency to a submodule for use. You can us
 ```nix{11}
 {
   inputs = {
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
     another-input.url = "github:username/repo-name/branch-name";
   };
 
@@ -132,7 +132,7 @@ Or you can achieve the same effect using the `_module.args` option:
 ```nix{13}
 {
   inputs = {
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
     another-input.url = "github:username/repo-name/branch-name";
   };
   outputs = inputs@{ self, nixpkgs, another-input, ... }: {
@@ -186,7 +186,7 @@ First, add the helix input data source to `flake.nix`:
 ```nix{6,11,17}
 {
   inputs = {
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
 
     # helix editor, use the master branch
     helix.url = "github:helix-editor/helix/master";
@@ -278,11 +278,11 @@ the following official/semi-official documents:
 
 [nix flake - Nix Manual]:
   https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake#flake-inputs
-[nixpkgs/flake.nix]: https://github.com/NixOS/nixpkgs/tree/nixos-25.05/flake.nix
+[nixpkgs/flake.nix]: https://github.com/NixOS/nixpkgs/tree/nixos-25.11/flake.nix
 [nixpkgs/nixos/lib/eval-config.nix]:
-  https://github.com/NixOS/nixpkgs/tree/nixos-25.05/nixos/lib/eval-config.nix
+  https://github.com/NixOS/nixpkgs/tree/nixos-25.11/nixos/lib/eval-config.nix
 [Module System - Nixpkgs]:
-  https://github.com/NixOS/nixpkgs/blob/nixos-25.05/doc/module-system/module-system.chapter.md
+  https://github.com/NixOS/nixpkgs/blob/nixos-25.11/doc/module-system/module-system.chapter.md
 [nixpkgs/nixos-25.05/lib/modules.nix - _module.args]:
   https://github.com/NixOS/nixpkgs/blob/nixos-25.05/lib/modules.nix#L122-L184
 [nixpkgs/nixos-25.05/nixos/doc/manual/development/option-types.section.md#L268-L275]:

docs/en/nixos-with-flakes/nixos-flake-configuration-explained.md

@@ -12,8 +12,8 @@ dependencies of this flake. These dependencies will be passed as arguments to th
 ```nix{2-5,7}
 {
   inputs = {
-    # NixOS official package source, using the nixos-25.05 branch here
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+    # NixOS official package source, using the nixos-25.11 branch here
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
   };
 
   outputs = { self, nixpkgs, ... }@inputs: {
@@ -45,8 +45,8 @@ results of the flake:
   description = "A simple NixOS flake";
 
   inputs = {
-    # NixOS official package source, here using the nixos-25.05 branch
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+    # NixOS official package source, here using the nixos-25.11 branch
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
   };
 
   outputs = { self, nixpkgs, ... }@inputs: {
@@ -140,8 +140,8 @@ definition includes the `lib` attribute, and in our example, we use the `lib` at
 ```nix{8-13}
 {
   inputs = {
-    # NixOS official package source, here using the nixos-25.05 branch
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
+    # NixOS official package source, here using the nixos-25.11 branch
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
   };
 
   outputs = { self, nixpkgs, ... }@inputs: {
@@ -158,8 +158,10 @@ definition includes the `lib` attribute, and in our example, we use the `lib` at
 The attribute set following `nixpkgs.lib.nixosSystem` is the function’s single argument,
 holding all configuration parameters; here we provide only two:
 
-- `system`: A legacy alias for `nixpkgs.hostPlatform` that specifies the platform the machine runs on.  
-  Because the generated `hardware-configuration.nix` (imported by `configuration.nix`) already defines this value, you can usually omit it here.
+- `system`: A legacy alias for `nixpkgs.hostPlatform` that specifies the platform the
+  machine runs on.  
+  Because the generated `hardware-configuration.nix` (imported by `configuration.nix`)
+  already defines this value, you can usually omit it here.
 - `modules`: This is a list of modules, where the actual NixOS system configuration is
   defined. The `/etc/nixos/configuration.nix` configuration file itself is a Nixpkgs
   Module, so it can be directly added to the `modules` list for use.
@@ -173,11 +175,11 @@ source code, and study its implementation.
 
 [nix flake - Nix Manual]:
   https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake#flake-inputs
-[nixpkgs/flake.nix]: https://github.com/NixOS/nixpkgs/tree/nixos-25.05/flake.nix
+[nixpkgs/flake.nix]: https://github.com/NixOS/nixpkgs/tree/nixos-25.11/flake.nix
 [nixpkgs/nixos/lib/eval-config.nix]:
-  https://github.com/NixOS/nixpkgs/tree/nixos-25.05/nixos/lib/eval-config.nix
+  https://github.com/NixOS/nixpkgs/tree/nixos-25.11/nixos/lib/eval-config.nix
 [Module System - Nixpkgs]:
-  https://github.com/NixOS/nixpkgs/blob/nixos-25.05/doc/module-system/module-system.chapter.md
+  https://github.com/NixOS/nixpkgs/blob/nixos-25.11/doc/module-system/module-system.chapter.md
 [nixpkgs/nixos-25.05/lib/modules.nix - _module.args]:
   https://github.com/NixOS/nixpkgs/blob/nixos-25.05/lib/modules.nix#L122-L184
 [nixpkgs/nixos-25.05/nixos/doc/manual/development/option-types.section.md#L268-L275]: