Skip to content
Dev Tools Release

NixOS 26.05 Modernizes Boot and Sunsets Intel Macs

The Yarara release defaults to systemd in stage 1 and sets a hard deadline for legacy Apple hardware.

Lenn Voss
Lenn Voss
Cloud & Infrastructure Writer · Jun 29, 2026 · 5 min read
NixOS 26.05 Modernizes Boot and Sunsets Intel Macs

NixOS has always occupied a unique space in the developer ecosystem. It is either praised as the ultimate tool for reproducible environments or avoided due to its steep learning curve and idiosyncratic architecture. The release of NixOS 26.05, codenamed "Yarara," shows a project actively trying to bridge that gap by standardizing its internals and shedding legacy platforms.

Managed by release managers yayayayaka and jopejoe1, this release is not just a routine package bump. While it includes the usual massive churn of packages, the real story for developers lies in two architectural decisions: defaulting to systemd for stage 1 boot and officially deprecating Intel Mac support. These moves signal a transition from bespoke, custom-scripted infrastructure toward standardized, modern systems.

The systemd Stage 1 Standardization

The boot process of a Linux system is split into stages. Stage 1, or the initial ramdisk (initrd), is responsible for mounting the root filesystem and preparing the system to hand over control to the main init system. Historically, NixOS relied on a custom, scripted bash implementation for this phase.

In NixOS 26.05, stage 1 is now based on systemd by default. The old scripted implementation is officially deprecated and scheduled for complete removal in version 26.11.

For developers who build custom virtual machine images, run NixOS on bare metal, or manage complex storage layouts, this is a major improvement. Debugging a failed boot in the old scripted initrd was a painful exercise in reading custom shell scripts. By moving to systemd, the early boot process becomes declarative and inspectable using the same tools developers use in user space.

This change means you can now define early-boot services, targets, and mounts using standard systemd syntax within your Nix configuration. If a mount fails or a network interface does not come up during the initrd phase, you can drop into a systemd emergency shell and use familiar commands to diagnose the issue. It brings consistency to the entire lifecycle of the operating system, from the first second of boot to shutdown.

The Intel Mac Runway Shrinks

For development teams that use the Nix package manager to maintain identical development shells across Linux and macOS, NixOS 26.05 delivers a clear warning: the Intel Mac era is over.

This release is the final version of Nixpkgs to support the x86_64-darwin architecture. The release team cited Apple's deprecation of the platform, limited build infrastructure, and developer time as the primary reasons for dropping support. Binaries will still be built and packages maintained until this release goes out of support at the end of 2026, but version 26.11 will drop Intel Mac support entirely.

If your organization still relies on older Intel-based MacBooks for local development or uses them as self-hosted CI runners, you have a clear deadline. To maintain a unified Nix-based workflow, you must migrate those workloads to Apple Silicon (aarch64-darwin) or standard Linux systems before the end of the year.

While this change is painful for teams with legacy hardware, it is a pragmatic decision for the Nix maintainers. Maintaining macOS support is notoriously difficult due to Apple's restrictive licensing and hardware requirements for build farms. Focusing resources on Apple Silicon allows the community to optimize the developer experience where the vast majority of macOS developers actually work.

Toolchains and Package Churn

Beyond the architectural shifts, NixOS 26.05 ships with updated compilers and libraries that will impact native development. GCC has been updated to version 15, while LLVM remains at version 21. Developers compiling C and C++ codebases will need to test their builds against the new GCC version to catch any new compiler warnings or deprecations.

The sheer volume of package updates in this release highlights the scale of the Nixpkgs repository. The release contributors added 20,442 new packages, updated 20,641 existing ones, and removed 17,532 outdated packages. This aggressive pruning keeps the repository maintainable and secure, but it also underscores the importance of using Nix flakes or pinning your channels to avoid unexpected breakages during local development.

For desktop users, the default GNOME environment has been updated to version 50, codenamed "Tokyo," which brings improved display handling and accessibility enhancements.

Migration and Support Windows

If you are running the previous release, 25.11 "Xantusia," you need to plan your upgrade quickly. That release is now deprecated and will reach its end-of-life on June 30, 2026.

Upgrading to 26.05 is straightforward for most configurations, but you should explicitly check your configuration files for any custom stage 1 overrides. If you have custom scripts hooked into the legacy initrd, you will need to rewrite them as systemd services to prepare for the eventual removal of the scripted stage 1 in 26.11.

To update your system channel to the new release, you can run:

nix-channel --add https://nixos.org/channels/nixos-2605 nixos
nixos-rebuild switch

If you are using Nix flakes, update your inputs.nixpkgs.url to point to the nixos-26.05 branch and run nix flake update.

The Verdict

NixOS 26.05 is a highly practical release. By standardizing on systemd for early boot and dropping the burden of Intel Mac support, the project is cleaning up its technical debt. For developers, this means a more predictable system configuration and a clearer path forward for cross-platform environments, even if it requires upgrading some legacy hardware along the way.

Sources & further reading

  1. NixOS 26.05 — nixos.org
Lenn Voss
Written by
Lenn Voss · Cloud & Infrastructure Writer

Lenn writes about cloud platforms, Kubernetes internals, and the infrastructure decisions that quietly make or break engineering organizations. Based in Berlin's vibrant tech scene, they have a talent for turning dense platform-engineering topics into prose that people actually finish reading.

Discussion 0

Join the discussion

Sign in or create an account to comment and vote.

No comments yet

Be the first to weigh in.

Related Reading