Problem
First off, thank you for maintaining NixOS-WSL. It makes running NixOS under WSL much easier, and the release branches and artifacts are especially helpful for users who follow stable NixOS releases.
NixOS 26.05 "Yarara" was released on 2026-05-30: https://nixos.org/blog/announcements/2026/nixos-2605/
NixOS-WSL currently appears to have release branches and release artifacts through 25.11, with the latest release being 2511.7.1. Users who want to follow the current stable NixOS release do not yet have an obvious release-26.05 branch or matching .wsl release artifact to use.
This is especially relevant because 25.11 is now in its deprecation window and reaches end of life on 2026-06-30, according to the 26.05 announcement.
Solution
Could NixOS-WSL add NixOS 26.05 support when the maintainers have bandwidth?
It would be helpful to have a release-26.05 branch, a matching .wsl release artifact, and updated docs or release notes for channel and flake users. If there are known blockers for 26.05, documenting those would also help users decide whether to stay on 25.11 for now.
Problem
First off, thank you for maintaining NixOS-WSL. It makes running NixOS under WSL much easier, and the release branches and artifacts are especially helpful for users who follow stable NixOS releases.
NixOS 26.05 "Yarara" was released on 2026-05-30: https://nixos.org/blog/announcements/2026/nixos-2605/
NixOS-WSL currently appears to have release branches and release artifacts through 25.11, with the latest release being
2511.7.1. Users who want to follow the current stable NixOS release do not yet have an obviousrelease-26.05branch or matching.wslrelease artifact to use.This is especially relevant because 25.11 is now in its deprecation window and reaches end of life on 2026-06-30, according to the 26.05 announcement.
Solution
Could NixOS-WSL add NixOS 26.05 support when the maintainers have bandwidth?
It would be helpful to have a
release-26.05branch, a matching.wslrelease artifact, and updated docs or release notes for channel and flake users. If there are known blockers for 26.05, documenting those would also help users decide whether to stay on 25.11 for now.