Hey everyone, we are Leona Maroni and Tristan Ross, the release managers of the newest release of NixOS. We are very proud to announce the public availability of NixOS 25.05 "Warbler". NixOS is a Linux distribution. Its underlying package repository Nixpkgs can also be used on other Linux systems and macOS with the Nix package manager. This release will receive bugfixes and security updates for seven months (up until 2025-12-31). The old release 24.11 "Vicuña" is now officially deprecated and will reach its end-of-life and stop receiving security updates after 2025-06-30. * NixOS Release Notes * Highlights * New Services * Backward Incompatibilities * Other Notable Changes * Nixpkgs Release Notes * Highlights * Backward Incompatibilities * Other Notable Changes * Nixpkgs Library * Upgrade Instructions * ISO Image Downloads The 25.05 release was made possible due to the efforts of **2857** contributors, who authored **57054** commits since the previous release. ## Highlights NixOS is already known as the most up to date distribution while also being the distribution with the most packages. This release of Nixpkgs * Added 7840 new packages * Updated 28054 existing packages * Removed 1694 outdated packages, in an effort to keep the package set maintainable and secure. In addition to packages from Nixpkgs, the NixOS Linux distribution also features composable configuration modules and integration tests for distributed systems. This release of NixOS * Added 137 new modules and 1930 configuration options * Removed 10 outdated modules and 215 configuration options. ### GNOME 48 GNOME has been updated to version 48 "Bengaluru", which introduces notification stacking, a new music player, HDR support, and more changes. Refer to the release notes for more details. ### Kernel The default Linux kernel has been updated from 6.6 to 6.12. All supported kernels remain available. ### C compilers LLVM has been updated to version 19. GCC has been updated to version 14. ## Special Thanks We want to personally thank * Seth and raf for editorializing the release notes * Yohann Boniface for the release logo * The NixOS infrastucture team for their dutifully tending to our build infrastructure * The Nixpkgs staging team for supporting our staging cycles and the patient fixing of many build errors. We also want to thank all contributors who made this release possible! ## Reflections and closing We are grateful for the opportunity to support the community as release managers and to learn about and participate in the release process. Seeing all the contributors working in their area of the project to improve it has been an exciting experience. We would like to thank everyone in the community for that. We are looking forward to the next release, NixOS 25.11 "Xantusia".

## History The NixOS logo was originally designed by Simon Frankau for Haskell as part of the 2009 Haskell logo contest. Simon kindly gave permission for the design to be used by the NixOS project, and it was made official in November 2009. In 2015, a new version of the logo with a "hexagon design" was created by Tim Cuthbertson and added to the homepage. In March of 2017, it officially superseded the previous logo and was added to the nixos-artwork repository. Over the years, there have been many updates to the logo and repository, including: * Converting the logotype to paths, removing the dependency on users having the designated font installed. * Adding documentation about the font used to create the logotype, guide layers, and colors * Introducing various logo variants, including a vertical variant, an all-white variant, and a rainbow variant ## Motivation to change An incredible amount of work has gone into creating and improving the logo and its documentation. However, it suffers from some inconsistencies and many parts of it are still ambiguous. The image below is a zoomed in view of the bottom of the NixOS logo with a horizontal line drawn starting at the bottom left of the snowflake. If you open the image and zoom in, you will see that the edges of the snowflake are not parallel to the horizontal line. Additionally, the edges of the snowflake are not collinear with each other. <img src="/images/blog/announcements/nixos-lambdas-not-collinear.jpg" alt="A zoomed in view of the bottom of the NixOS logo showing that the lambdas are not collinear or flat." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> The image below shows the paths that define the gradient for the lambdas. There are two gradient definitions that are different and ideally they would be the same. <img src="/images/blog/announcements/nixos-lambda-two-gradient-defs.jpg" alt="A view of the NixOS logo source showing two gradient definitions." style="display: block; margin: 0 auto; float: none; max-width: 40%; height: auto;" decoding="async" loading="lazy" /> When creating a brand guide, there are usually sections describing the anatomy of the logo, clearspace, sizing, alignment, variations, and misuse. Some of this information has been captured in the README co-located with the logos but not all of it is well defined. For example: * The anatomy of the logo is not well defined which should include information like the relative size of the logomark and logotype and the spacing between them. * The anatomy of the logomark is not well defined which should include information like the dimensions of the lambdas and the gap between lambdas. * The anatomy of the logotype is not well defined which should include information like spacing between glyphs. * The paths used to define the gradients of the lambdas are not well defined and are different. * The clearspace around the logo and logomark is not well defined. * The clearspace around the logo and logomark is not sufficient. * There are no guidelines about sizing and alignment. * There is no variation of the logotype by itself. * There are no guidelines about creating new variations. * There are no guidelines about misuse. ## Work towards improvement To address these issues, I want to improve how we create logos, create a Branding Guide, and create a Media Kit. Before I started any design work, I tried to find a tool that would satisfy my 2 requirements: 1. I have to be able to design the logo parametrically. 2. I have to be able to generate SVG files programmatically. The idea behind the first requirement was that I want to be able to reduce the creation of the logo to a few simple parameters. Additionally, if I can generate the SVG files programmatically, I can programmatically generate the Branding Guide and Media Kit. I'm calling this approach **"Branding as Code" (BaC)** I surveyed many FOSS image editing and CAD tools but none of them could satisfy both my requirements. In the end, I decided to create my own tooling in Python. After three months of work the tooling has a lot of capabilities. It can: * Generate a lambda based on 3 parameters: radius, thickness, and gap. * Generate a logomark with different colors and color styles. * Generate a logotype with different colors and styles. * Generate a logo (logomark + logotype) in different layouts. * Generate all three logo products with different clearspace values and meaningfully unique filenames. * Generate dimensioned and annotated SVG files for use in the Branding Guide. A few example output products are shown below. <img src="/images/blog/announcements/nixos-lambda-dimensioned-linear.svg" alt="A lambda from the NixOS logomark with linear dimensions shown." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> <img src="/images/blog/announcements/nixos-lambda-gradient-dimensioned.svg" alt="The gradient paths of the NixOS logomark with dimensions shown." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> <img src="/images/blog/announcements/nixos-lambda-gradient-background.svg" alt="The gradient paths of the NixOS logomark with dimensions shown and the gradient overlaid." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> <img src="/images/blog/announcements/nixos-snowflake-dimensioned-linear.svg" alt="The NixOS logomark with linear dimensions shown." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> There is still much more work to be done including: generating many more annotated drawings for the Branding Guide, creating the Branding Guide, and creating the Media Kit. I would like to thank Ida Bzo, Sebastian Kraus, Ross Turk, and David Nuon for their feedback and assistance throughout this process. This is just the beginning of building a more precise, flexible, and scalable visual identity for the NixOS project.

## History The NixOS logo was originally designed by Simon Frankau for Haskell as part of the 2009 Haskell logo contest. Simon kindly gave permission for the design to be used by the NixOS project, and it was made official in November 2009. In 2015, a new version of the logo with a "hexagon design" was created by Tim Cuthbertson and added to the homepage. In March of 2017, it officially superseded the previous logo and was added to the nixos-artwork repository. Over the years, there have been many updates to the logo and repository, including: * Converting the logotype to paths, removing the dependency on users having the designated font installed. * Adding documentation about the font used to create the logotype, guide layers, and colors * Introducing various logo variants, including a vertical variant, an all-white variant, and a rainbow variant ## Motivation to change An incredible amount of work has gone into creating and improving the logo and its documentation. However, it suffers from some inconsistencies and many parts of it are still ambiguous. The image below is a zoomed in view of the bottom of the NixOS logo with a horizontal line drawn starting at the bottom left of the snowflake. If you open the image and zoom in, you will see that the edges of the snowflake are not parallel to the horizontal line. Additionally, the edges of the snowflake are not collinear with each other. <img src="/images/blog/announcements/nixos-lambdas-not-collinear.jpg" alt="A zoomed in view of the bottom of the NixOS logo showing that the lambdas are not collinear or flat." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> The image below shows the paths that define the gradient for the lambdas. There are two gradient definitions that are different and ideally they would be the same. <img src="/images/blog/announcements/nixos-lambda-two-gradient-defs.jpg" alt="A view of the NixOS logo source showing two gradient definitions." style="display: block; margin: 0 auto; float: none; max-width: 40%; height: auto;" decoding="async" loading="lazy" /> When creating a brand guide, there are usually sections describing the anatomy of the logo, clearspace, sizing, alignment, variations, and misuse. Some of this information has been captured in the README co-located with the logos but not all of it is well defined. For example: * The anatomy of the logo is not well defined which should include information like the relative size of the logomark and logotype and the spacing between them. * The anatomy of the logomark is not well defined which should include information like the dimensions of the lambdas and the gap between lambdas. * The anatomy of the logotype is not well defined which should include information like spacing between glyphs. * The paths used to define the gradients of the lambdas are not well defined and are different. * The clearspace around the logo and logomark is not well defined. * The clearspace around the logo and logomark is not sufficient. * There are no guidelines about sizing and alignment. * There is no variation of the logotype by itself. * There are no guidelines about creating new variations. * There are no guidelines about misuse. ## Work towards improvement To address these issues, I want to improve how we create logos, create a Branding Guide, and create a Media Kit. Before I started any design work, I tried to find a tool that would satisfy my 2 requirements: 1. I have to be able to design the logo parametrically. 2. I have to be able to generate SVG files programmatically. The idea behind the first requirement was that I want to be able to reduce the creation of the logo to a few simple parameters. Additionally, if I can generate the SVG files programmatically, I can programmatically generate the Branding Guide and Media Kit. I'm calling this approach **"Branding as Code" (BaC)** I surveyed many FOSS image editing and CAD tools but none of them could satisfy both my requirements. In the end, I decided to create my own tooling in Python. After three months of work the tooling has a lot of capabilities. It can: * Generate a lambda based on 3 parameters: radius, thickness, and gap. * Generate a logomark with different colors and color styles. * Generate a logotype with different colors and styles. * Generate a logo (logomark + logotype) in different layouts. * Generate all three logo products with different clearspace values and meaningfully unique filenames. * Generate dimensioned and annotated SVG files for use in the Branding Guide. A few example output products are shown below. <img src="/images/blog/announcements/nixos-lambda-dimensioned-linear.svg" alt="A lambda from the NixOS logomark with linear dimensions shown." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> <img src="/images/blog/announcements/nixos-lambda-gradient-dimensioned.svg" alt="The gradient paths of the NixOS logomark with dimensions shown." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> <img src="/images/blog/announcements/nixos-lambda-gradient-background.svg" alt="The gradient paths of the NixOS logomark with dimensions shown and the gradient overlaid." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> <img src="/images/blog/announcements/nixos-snowflake-dimensioned-linear.svg" alt="The NixOS logomark with linear dimensions shown." style="display: block; margin: 0 auto; float: none; max-width: 100%; height: auto;" decoding="async" loading="lazy" /> All of these efforts - and the ones still underway - are being done to serve the community, which truly deserves to be treated as a mature and important organization. In today’s world, a clear visual identity and coherent narrative are must-haves for any serious project. Meeting the requirements of modern communication and marketing practices isn't about following trends for their own sake; it’s about giving NixOS the tools it needs to thrive and be recognized alongside other respected projects. We’re taking the steps that are expected - and needed - to ensure the health and growth of the project. Many other communities that invested early in structured branding benefit from easier outreach, clearer communication, and a stronger sense of belonging. On the other hand, projects that neglected this aspect have often faced issues with fragmentation, public confusion, and difficulty attracting new users and contributors. We're choosing the path that sets NixOS up for long-term success, while staying true to the spirit of openness and excellence that defines this community. There is still much more work to be done including: generating many more annotated drawings for the Branding Guide, creating the Branding Guide, and creating the Media Kit. I would like to thank Ida Bzo, Sebastian Kraus, Ross Turk, and David Nuon for their feedback and assistance throughout this process. This is just the beginning of building a more precise, flexible, and scalable visual identity for the NixOS project. Daniel Baker Brand and Design Steward

### A New Chapter for the NixOS Foundation On March 4th, 2025, we welcomed a new NixOS Foundation Board — marking the first-ever board rotation under our newly established constitution. Change is always a big step, but we believe this one is for the better! With clearly defined roles and a more structured approach, the Foundation is set up for success in supporting the Nix & NixOS ecosystem. Following a thorough selection process, carefully coordinated with the Steering Committee, the new board members are: * President/Chair: Ron Efroni Rotman (continuing role) (@ron) * Secretary: Silvan Mosberger (@infinisil) * Director of Legal Affairs: Ryan Trinkle (@ryantrinkle) * Treasurer: Maximilian Habryka (@lassulus) * Director of Community Support: Sebastian Kraus (@ra33it0) This team is at the heart of the Foundation’s mission — to strengthen and support the Nix & NixOS community. ### A Huge Thank You To everyone who participated — whether by nominating, giving feedback, or simply showing support—your engagement made this possible. Seeing so many community members step up to contribute has been truly inspiring! ### What’s Next? * Legal Handover – The transition process with the KVK in Utrecht is underway. * Onboarding & Operations – In the coming weeks and months, we’ll focus on getting the new board fully onboarded and operational. Looking forward to an exciting future — together!

Hello everyone, we are Tristan Ross and Weijia Wang, the release managers for the newest release of NixOS known as NixOS 24.11 Vicuña. We're glad to announce that after the additional week-long delay that we can deliver this stable release of NixOS. NixOS is a Linux distribution, whose set of packages can also be used on other Linux systems and macOS. This release will receive bugfixes and security updates for seven months (up until 2025-06-31). * Release manual * Highlights * New Services * Backward Incompatibilities * Other Notable Changes * Upgrade Instructions * ISO Image Downloads The 24.11 release was made possible due to the efforts of **2669** contributors, who authored **49079** commits since the previous release. Our thanks go the contributors who also take care of the continued stability and security of our stable release. NixOS is already known as the most up to date distribution while also being the distribution with the most packages. This release saw **8141 new** packages and **20975 updated** packages in Nixpkgs. We also **removed 3970** packages in an effort to keep the package set maintainable and secure. In addition to packages the NixOS distribution also features modules and tests that make it what it is. This release brought **119 new** modules and **removed 30**. In that process we **added 1706** options and **removed 556**. ### GNOME 47 GNOME has been updated to version 47 "Denver", which introduces accent colors, small screen support, screen capture hardware encoding, and more changes. Refer to the release notes for more details. ### Plasma 6 Plasma has been updated to version 6.2, which introduces many bug fixed and other changes. Refer to the release notes for more details. ### Darwin Rework Emily, Randy Eckenrode, and toonn did an amazing job with their work as the Darwin core maintainers to bring better support for Darwin into Nixpkgs. A comprehensive list of changes can be found on the NixOS Discourse under "The Darwin SDKs have been updated". ### C Compilers LLVM has been updated to version 19 and GCC remains the same version. Tristan Ross made many changes which improves the way we provide multiple versions of LLVM. ## Special thanks We want to personally thank seth and Priyanshu Tripathi for editorializing the release notes, lennart for doing the release logo, Vladimír Čunát for his tireless effort in managing jobsets and staging cycles, Martin Weinelt for dutifully tending to our build infrastructure, and Cole Helbling for his effort on keeping ofBorg running. ### Reflections and Closing We are thankful for everyone who contributed and everyone who was patient for 24.11. It has been a great time working with everyone to make this release possible. We hope everyone is looking forward to the next release, NixOS 25.05 Warbler.

After successfully using CIVS to tally the 450 ballots cast (56% turnout) on OpaVote, We are hereby concluding this election! We congratulate the first members of the Nix Steering Committee (SC) (ordered alphabetically): * @Ericson2314 (2 year term) * @fpletz (1 year term) * @Gabriella439 (2 year term) * @jtojnar (2 year term) * @roberth (2 year term) * @tomberek (1 year term) * @winterqt (1 year term) This result is certified by all Election Committee members. For verification purposes, all OpaVote ballots will soon be available here (the result there should be ignored; voters will also get an email), while the CIVS tally to determine the result using the same ballots is already available here. See the new docs for more info on result verification. We are now establishing communications with the first SC members and will soon make a final handover announcement on behalf of the EC / NCA. We, the members of the EC / NCA, and Ron from the NixOS Foundation board, are thankful for everybody's participation in this first election, and are looking forward to see the first SC getting started. Note that you can also read and publicly discuss this announcement on Discourse.

As a first step towards a better governance for official Nix projects, we are happy to announce the kick-off of the first Nix Steering Committee election! The Steering Committee will be the primary community leadership body, responsible for steering the official Nix projects -- organisationally, socially, and technically. This includes making decisions over what is official, managing teams, approving NixOS Foundation policies relevant for the community, being the final escalation point, and more as detailed in the Nix Governance Constitution. While the Steering Committee is given the authority to make decisions within the scope of its responsibilities directly, it is expected to delegate as much as possible. Note that you can also read and publicly discuss this announcement on Discourse. ## Participating Automatically eligible voters will be sent an email and be added/invited to the @NixOS/voters-2024 GitHub team. If you're on the GitHub team but have not received an email, make sure to check and optionally update your email address. If you're neither on the GitHub team nor have received an email, you're likely not automatically eligible. In this case you may consider requesting an exception. Members of the GitHub team can: * Nominate themselves or others. * Endorse unconfirmed nominees that they'd like to be able to vote for. * Ask questions to nominees as the primary way of engaging with them. If you have any questions or need support, please get in touch with the Election Committee. ## Timeline * 2024-09-29 Sun: Deadline for nominations * 2024-10-01 Tue: Deadline for endorsements * 2024-10-03 Thu: Deadline for candidate questions * 2024-10-06 Sun: Deadline for candidate answers, submitting voter exceptions and updating voter email addresses * 2024-10-07 Mon: Voting starts * 2024-10-20 Sun: Voting ends * 2024-10-23 Wed: Results announced The results are expected to be announced just before NixCon 2024 in Berlin, which starts on 2024-10-25.

Initially published by petites singularités. English translation provided by OW2. If you want to sign the letter, please re-publish the original letter on your website and add to the list of signatories. Since 2020, Next Generation Internet (NGI) programmes, part of European Commission's Horizon programme, fund free software in Europe using a cascade funding mechanism (see for example NLnet's calls). This year, according to the Horizon Europe working draft detailing funding programmes for 2025, we notice that Next Generation Internet is not mentioned any more as part of Cluster 4. NGI programmes have shown their strength and importance to supporting the European software infrastructure, as a generic funding instrument to fund digital commons and ensure their long-term sustainability. We find this transformation incomprehensible, moreover when NGI has proven efficient and economical to support free software as a whole, from the smallest to the most established initiatives. This ecosystem diversity backs the strength of European technological innovation, and maintaining the NGI initiative to provide structural support to software projects at the heart of worldwide innovation is key to enforce the sovereignty of a European infrastructure. Contrary to common perception, technical innovations often originate from European rather than North American programming communities, and are mostly initiated by small-scaled organizations. Previous Cluster 4 allocated 27 million euros to: * "Human centric Internet aligned with values and principles commonly shared in Europe" ; "A flourishing internet, based on common building blocks created within NGI, that enables better control of our digital life" ; * "A structured ecosystem of talented contributors driving the creation of new internet commons and the evolution of existing internet commons". In the name of these challenges, more than 500 projects received NGI funding in the first 5 years, backed by 18 organisations managing these European funding consortia. NGI contributes to a vast ecosystem, as most of its budget is allocated to fund third parties by the means of open calls, to structure commons that cover the whole Internet scope - from hardware to application, operating systems, digital identities or data traffic supervision. This third-party funding is not renewed in the current program, leaving many projects short on resources for research and innovation in Europe. Moreover, NGI allows exchanges and collaborations across all the Euro zone countries as well as "widening countries" [^1], currently both a success and an ongoing progress, likewise the Erasmus programme before us. NGI also contributes to opening and supporting longer relationships than strict project funding does. It encourages implementing projects funded as pilots, backing collaboration, identification and reuse of common elements across projects, interoperability in identification systems and beyond, and setting up development models that mix diverse scales and types of European funding schemes. While the USA, China or Russia deploy huge public and private resources to develop software and infrastructure that massively capture private consumer data, the EU can't afford this renunciation. Free and open source software, as supported by NGI since 2020, is by design the opposite of potential vectors for foreign interference. It lets us keep our data local and favors a community-wide economy and know-how, while allowing an international collaboration. This is all the more essential in the current geopolitical context: the challenge of technological sovereignty is central, and free software allows to address it while acting for peace and sovereignty in the digital world as a whole. In this perpective, we urge you to claim for preserving the NGI programme as part of the 2025 funding programme. [^1]: As defined by Horizon Europe, widening Member States are Bulgaria, Croatia, Cyprus, the Czech Republic, Estonia, Greece, Hungary, Latvia, Lituania, Malta, Poland, Portugal, Romania, Slovakia and Slovenia. Widening associated countries (under condition of an association agreement) include Albania, Armenia, Bosnia, Feroe Islands, Georgia, Kosovo, Moldavia, Montenegro, Morocco, North Macedonia, Serbia, Tunisia, Turkey and Ukraine. Widening overseas regions are : Guadeloupe, French Guyana, Martinique, Reunion Island, Mayotte, Saint-Martin, The Azores, Madeira, the Canary Islands.

We're happy to announce that **NixCon 2024** , will take place **October 25-27 2024 in Berlin** For more information, see the NixCon 2024 website. And please consider submitting a talk! Follow the discussion on discourse: NixCon Announcement, CFP Announcement

Hey everyone, we are Weijia Wang and Jörg Thalheim, the release managers for this stable release and we are very proud to announce the public availability of NixOS 24.05 “Uakari”. NixOS is a Linux distribution, whose set of packages can also be used on other Linux systems and macOS. This release will receive bugfixes and security updates for seven months (up until 2024-12-31). * Release manual * Highlights * New Services * Backward Incompatibilities * Other Notable Changes * Upgrade Instructions * ISO Image Downloads The 24.05 release was made possible due to the efforts of **2491** contributors, who authored **47795** commits since the previous release. Our thanks go the contributors who also take care of the continued stability and security of our stable release. NixOS is already known as the most up to date distribution while also being the distribution with the most packages. This release saw **17777 new** packages and **16249 updated** packages in Nixpkgs. We also **removed 9393** packages in an effort to keep the package set maintainable and secure. In addition to packages the NixOS distribution also features modules and tests that make it what it is. This release brought **145 new** modules and **removed 23**. In that process we **added 1983** options and **removed 304**. ### GNOME 46 GNOME has been updated to version 46 "Kathmandu", which introduces experimental VRR support, WebDAV support in Online Accounts, and more changes. Refer to the release notes for more details. ### Plasma 6 Plasma has been updated to version 6.0, which introduces new defaults, refreshed Breeze, and more changes. Refer to the release notes for more details. ### Linux Kernel 6.6 The default kernel package has been updated from 6.1 to 6.6. All supported kernels since 4.19 remain available. ### Special Thanks We want to personally thank Jacek Generowicz for editorializing the release notes, Lennart Mühlenmeier for doing the release logo, Vladimír Čunát for his tireless effort in managing jobsets and staging cycles, Martin Weinelt for dutifully tending to our build infrastructure, and Cole Helbling for his effort on keeping ofBorg running. ### Reflections and Closing We are very thankful for this opportunity to learn about and participate in the release process. It has been an awesome experience to work with everyone on this release, and we want to say thank you to everyone in this community that built NixOS and helped made this release better.

Hey everyone, we are figsoda and Ryan Lahfa, the release managers for this stable release and we are very proud to announce the public availability of NixOS 23.11 “Tapir”. This release will receive bugfixes and security updates for seven months (up until 2024-06-30). * Release manual * NixOS breaking changes * New NixOS services * Other notable NixOS changes * Nixpkgs library breaking changes * Nixpkgs library additions and improvements * Nixpkgs library deprecations * Upgrade Instructions * ISO Image Downloads The 23.11 release was made possible due to the efforts of **2162** contributors, who authored **40024** commits since the previous release. Our thanks go the contributors who also take care of the continued stability and security of our stable release. NixOS is already known as the most up to date distribution while also being the distribution with the most packages. This release saw **9147 new** packages and **18700 updated** packages in Nixpkgs. We also **removed 4015** packages in an effort to keep the package set maintainable and secure. In addition to packages the NixOS distribution also features modules and tests that make it what it is. This release brought **113 new** modules and **removed 18**. In that process we **added 1565** options and **removed 362**. ### GNOME 45 GNOME has been updated to version 45 "Rīga", which introduces a new image viewer, a new camera app, and more changes. Refer to the release notes for more details. ### Default LLVM Version The default version for the LLVM package set has been updated to 16 (from 11) on both Linux and Darwin, which introduced lots of new features and improvements. The full lists of changes are available here (LLVM) and here (Clang). ### Special Thanks We want to personally thank Alejandro Sánchez Medina and Lennart Mühlenmeier for editorializing the release notes, Vladimír Čunát for his tireless effort in managing jobsets, staging cycles and build infrastructure, Cole Helbling for his epic effort in bisecting kernel issues with ARM64 for our remote builders, and Graham Christensen for dutifully tending to our build infrastructure. ### Reflections and Closing I am very thankful for this opportunity to learn about and participate in the release process. It has been an awesome experience to work with everyone on this release, and I want to say thank you to everyone in this community that built NixOS and helped made this release better.

Hey everyone, we are Ryan Lahfa and Martin Weinelt, the release managers for this stable release and we are very proud to announce the public availability of NixOS 23.05 “Stoat”. This release will receive bugfixes and security updates for seven months (up until 2023-12-31). * Release manual * Highlights * New Services * Backward Incompatibilities * Other Notable Changes * Nixpkgs internals * Detailed migration information * Upgrade Instructions * ISO Image Downloads The 23.05 release was made possible due to the efforts of **1867** contributors, who authored **36566** commits since the previous release. Our thanks go the contributors who also take care of the continued stability and security of our stable release. NixOS is already known as the most up to date distribution while also being the distribution with the most packages. This release saw **16240 new** packages and **13524 updated** packages in Nixpkgs. We also **removed 13466** packages in an effort to keep the package set maintainable and secure. In addition to packages the NixOS distribution also features modules and tests that make it what it is. This release brought **282 new** modules and **removed 183**. In that process we **added 2882** options and **removed 728**. ### Removal of weak hashing algorithms The support for weak password hashing algorithms through the `crypt(3)` API was disabled in NixOS 23.05. We consider password hashing methods weak if the libxcrypt project did not flag them strong. This change affects user accounts on the local system, as well as the supported algorithms in many applications that rely on that API. Examples are authentication services like OpenLDAP or PAM, databases like PostgreSQL and, more generally speaking, programming languages that offer a password hashing interface like Python. These applications should be migrated away from weak password hashes before upgrading to NixOS 23.05, as the lack of support for these algorithms may make authentication for these applications impossible. If your system has user accounts that rely on such weak hashing algorithms, a warning will be emitted during activation. Existing users accounts are most likely using sha512crypt, for which the hash is prefixed with _$6$_. These will continue to work for the foreseeable future, but migrating to more modern hashes is strongly recommended anyway. Interactively configured passwords can be updated using **passwd** , new password hashes can be generated through **mkpasswd**. Note, that we do offer `libxcrypt-legacy` as an escape hatch, that affected packages can be overridden with. ### Bootspec (RFC-125) As part of standardization efforts in RFC 125, also called "Bootspec", all new users have a `boot.json` file in their system top-level derivation, you can check the one on the system you are running in _/run/current-system/boot.json_ for example. The idea behind Bootspec is to enable new boot usecases in NixOS: UEFI Secure Boot, unifying bootloader installer scripts, multiple initrds or systemd system extensions and A/B schemas. ### Special Thanks We want to personally thank Lennart Mühlenmeier and Winter for editorializing the release notes, Vladimír Čunát for his tireless effort in managing jobsets, staging cycles and build infrastructure, Cole Helbling for his epic effort in bisecting kernel issues with ARM64 for our remote builders, and Graham Christensen for dutifully tending to our build infrastructure. ### Reflections and Closing I am very grateful for being given the opportunity to learn about the release process and run it with the help of everyone in the NixOS community. It has been a very exciting ride and witnessing the efforts of everyone poured in the project made me want to work towards supporting those efforts in many areas of the project, e.g. CI, infrastructure and more. Now that the process documentation has reached, in my experience, a high level of maturity. I believe it is now time for tooling to become consolidated, professional, comfortable and helpful for release managers and editors but also to all the persons close to the release process. As a previous release manager said it, the release process shall become only more boring in the future!

Hey everyone, we are Martin Weinelt and Janne Heß, the release managers for this stable release and we are very proud to announce the public availability of NixOS 22.11 “Raccoon”. This release will receive bugfixes and security updates for seven months (up until 2023-06-30). * Release manual * Highlights * Internal changes * Notable version Updates * Backward Incompatibilities * Other Notable Changes * New Services * Upgrade Instructions * ISO Image Downloads The 22.11 release was made possible due to the efforts of **1652** contributors, who authored **30371** commits since the previous release. Our thanks go the contributors who also take care of the continued stability and security of our stable distribution. NixOS is already known as the most up to date distribution while also being the distribution with the most packages. This release saw **16678 new** packages and **14680 updated** packages in nixpkgs. We also **removed 2812** packages in an effort to keep the package set maintainable and secure. In addition to packages the NixOS distribution also features modules and tests that make it what it is. This release brought **91 new** modules and **removed 20**. In that process we **added 1322** options and **removed 487**. ### Password hashing migration During the NixOS 22.11 lifecycle old password hashes may need to be updated, because we plan to disable weak password hashes in NixOS 23.05. We consider password hashing methods weak, if the libxcrypt project did not flag them strong. If your system is configured with weak hashes a script will emit a warning during activation. We expect most users accounts to be set up with sha512crypt (hash prefixed with _$6$_) which we will continue to support. Interactively configured passwords can be updated using **passwd** , new password hashes can be generated through **mkpasswd**. ### aarch64-linux channel merge The separate aarch64-linux specific channels have been discontinued. Their jobs have been merged into the generic **nixos-22.11** and **nixos-22.11-small** channels and will thereby receive updates at the same time as their x86_64-linux counterparts. ### Special Thanks We want to personally thank Winter and Jörg Thalheim for editorializing the release notes, Vladimír Čunát for his tireless effort in managing jobsets and staging cycles, and Graham Christensen for dutifully tending to our build infrastructure. ### Reflections and Closing I'm thankful for being given the chance to guide the release process. It is an exciting experience and seeing the tremendous collaborative effort the community invests to make the release a success is inspiring. While previous release managers made great strides to document the process there are lots of steps that could be benefit from better documentation and more tooling. It is our hope that future release managers and the community will iterate further on this.

Hey everyone, I'm Janne Heß, the release manager for 22.05. As promised, the latest stable release is here: NixOS 22.05 “Quokka”. * Release manual * Highlights * New Services * Backward Incompatibilities * Other Notable Changes * Upgrade Instructions * Image downloads The 22.05 release was possible due to the efforts of **1611** contributors in **46727** commits. We would especially like to thank our top 10 contributors: Fabian Affolter, Sandro Jäckel, Martin Weinelt, Bobby Rong, Mario Rodas, Jonathan Ringer, Jan Tojnar, Jörg Thalheim, sternenseemann, and Robert Schütz. NixOS is already known as the most up to date distribution and is the distribution with the most packages. This release saw **9345 new** packages and **10666 updated** packages. Removal of unmaintained packages is also important to keep the package set working and secure. This release **removed 5874** packages that were available in 21.11. nixpkgs also includes a lot of modules that make NixOS what it is. This release brought **89 new** modules and **removed 27**. In that process, the contributors **added 1304** options and **removed 359**. ### Nix 2.8 This release brings nix 2.8 as the default nix package. This brings users a lot of fixes, general improvements and increased performance. The main feature that was awaited for a long time is the introduction of experimental features, namely the **flakes** experimental feature. Users still have to opt into the feature manually (as well as the **nix-command** feature that was enabled by default in previous nix versions). ### Graphical installer Improving experience for new users is something that the NixOS project has been working on for a long time. After all, NixOS is a very different compared to traditional distributions. To make it easier to get started with a new NixOS system, a graphical installer based on Calamares is now provided. This installer starts by default when launching the GNOME or Plasma ISO and allows for one-time configuration of a new system. ### Special Thanks Thanks to Jörg Thalheim who helped with the changelog as the release editor. Also to Jon Ringer for guiding the release process since NixOS 20.09. Vladimír Čunát and Martin Weinelt for their continued efforts managing and stabilizing staging. More thanks go out to Martin Weinelt for helping me with a lot of questions about the process and some subsystems, your help was greatly appreciated. Also thanks a lot to Graham Christensen for organizing with Equinix Metal to ensure we had enough compute resources and the entire infrastructure team. Additional thanks go out to Rick van Schijndel for going through all the pain of marking packages that do not build anymore as broken. I hope we can make the process more straightforward in future releases. ### Reflections and Closing This release brought a lot of features and improvements I've been waiting to see in a release channel. It was a great pleasure working with the community and seeing incredible amounts of work being done by the entire community.