Channel branches - Revision history

Blokyk: fix weird visual code split

2026-09-30T13:44:23Z

fix weird visual code split

← Older revision		Revision as of 13:44, 30 September 2026
Line 117:		Line 117:
	\|-		\|-
	\|<code>nixos-*-small</code>		\|<code>nixos-*-small</code>
	\|<code>/nixos/{major}.{minor}~~</code><code>~~-small/nixos-{full_version}/{artifact}</code>		\|<code>/nixos/{major}.{minor}-small/nixos-{full_version}/{artifact}</code>
	\|}		\|}
	<code>channels.nixos.org/{channel_name}</code> will redirect to the most recent release's directory of artifacts ([https://channels.nixos.org/nixos-unstable example]).		<code>channels.nixos.org/{channel_name}</code> will redirect to the most recent release's directory of artifacts ([https://channels.nixos.org/nixos-unstable example]).

Blokyk: Add more information about how channels are versioned, and how a user can determine that version string.

2026-09-30T13:16:09Z

Add more information about how channels are versioned, and how a user can determine that version string.

@@ Line 94: / Line 94: @@
 For the <code>NixOS</code> channel command-not-found index is generated, which can take some time since it has to fetch all packages. <code>nixpkgs</code> is quickly updated since none of the above needs to happen once a channel update is triggered.
 Updates for the -unstable channels typically take a few days after commits land in the master branch.
-To find out when a channel was last updated, check [https://status.nixos.org/ https://status.nixos.org/]. The progress of a particular pull request can be tracked via the (third-party) [https://nixpk.gs/pr-tracker.html Nixpkgs Pull Request Tracker].
+To find out when a channel was last updated, check https://status.nixos.org/. The progress of a particular pull request can be tracked via the (third-party) [https://nixpk.gs/pr-tracker.html Nixpkgs Pull Request Tracker].
 === Check build status ===

DHCP: /* Check build status */ use for shell command example

2026-06-01T12:28:49Z

Check build status: use <syntaxhighlight lang=console> for shell command example

← Older revision		Revision as of 12:28, 1 June 2026
Line 101:		Line 101:
	=== Check build status ===		=== Check build status ===
	[https://github.com/nix-community/hydra-check hydra-check]		[https://github.com/nix-community/hydra-check hydra-check]
	<syntaxhighlight lang="sh">		<syntaxhighlight lang="console">
	$ hydra-check --channel unstable bash		$ hydra-check --channel unstable bash
	Build Status for nixpkgs.bash.x86_64-linux on unstable		Build Status for nixpkgs.bash.x86_64-linux on unstable

Yayayayaka: Update NixOS channel name from 25.11 to 26.05

2026-05-26T11:23:44Z

Update NixOS channel name from 25.11 to 26.05

← Older revision		Revision as of 11:23, 26 May 2026
Line 8:		Line 8:

	* Stable vs unstable:		* Stable vs unstable:
	** '''Stable channels''' (e.g. <code>nixos-25.11</code>) only provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after the initial release. New stable channels are released every six months.		** '''Stable channels''' (e.g. <code>nixos-26.05</code>) only provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after the initial release. New stable channels are released every six months.
	** '''Unstable channels''' (e.g. <code>nixos-unstable</code>, <code>nixpkgs-unstable</code>) follow the <code>master</code> branch of Nixpkgs, delivering the latest tested updates on a rolling basis.		** '''Unstable channels''' (e.g. <code>nixos-unstable</code>, <code>nixpkgs-unstable</code>) follow the <code>master</code> branch of Nixpkgs, delivering the latest tested updates on a rolling basis.

	* Large vs small:		* Large vs small:
	** '''Large channels''' (e.g. <code>nixos-25.11</code>, <code>nixos-unstable</code>) are updated only after Hydra has finished building the full breadth of Nixpkgs.		** '''Large channels''' (e.g. <code>nixos-26.05</code>, <code>nixos-unstable</code>) are updated only after Hydra has finished building the full breadth of Nixpkgs.
	** '''Small channels''' (e.g. <code>nixos-25.11-small</code>, <code>nixos-unstable-small</code>) are identical to large channels, but are updated as soon as Hydra has finished building a defined set of commonly-used packages. Thus, users following these channels will get faster updates but may need to build any packages they use from outside the defined set themselves. These channels are intended to be used for server setups, for example.		** '''Small channels''' (e.g. <code>nixos-26.05-small</code>, <code>nixos-unstable-small</code>) are identical to large channels, but are updated as soon as Hydra has finished building a defined set of commonly-used packages. Thus, users following these channels will get faster updates but may need to build any packages they use from outside the defined set themselves. These channels are intended to be used for server setups, for example.

	For most users, a stable/large channel is recommended.		For most users, a stable/large channel is recommended.
Line 52:		Line 52:
	== Using channel branches with flakes ==		== Using channel branches with flakes ==

	Although [[Flakes]] do not make use of traditional Nix channels, they can still reference the same channel branches by specifying them in the flake’s inputs. These branches, such as <code>nixos-25.11</code> or <code>nixos-unstable</code>, correspond to named references within the Nixpkgs repository and serve a similar role in selecting which version of Nixpkgs or other inputs to use.		Although [[Flakes]] do not make use of traditional Nix channels, they can still reference the same channel branches by specifying them in the flake’s inputs. These branches, such as <code>nixos-26.05</code> or <code>nixos-unstable</code>, correspond to named references within the Nixpkgs repository and serve a similar role in selecting which version of Nixpkgs or other inputs to use.

	A simple example of defining channel branches in a flake:		A simple example of defining channel branches in a flake:
Line 59:		Line 59:
	{		{
	inputs = {		inputs = {
	nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";		nixpkgs.url = "github:nixos/nixpkgs/nixos-26.05";
	nixpkgs-unstable.url = "github:nixos/nixpkgs/nixos-unstable";		nixpkgs-unstable.url = "github:nixos/nixpkgs/nixos-unstable";
	};		};

Fijxu: Update nixos channel name from 25.05 to 25.11

2026-01-06T00:52:48Z

Update nixos channel name from 25.05 to 25.11

← Older revision		Revision as of 00:52, 6 January 2026
Line 8:		Line 8:

	* Stable vs unstable:		* Stable vs unstable:
	** '''Stable channels''' (e.g. <code>nixos-25.05</code>) only provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after the initial release. New stable channels are released every six months.		** '''Stable channels''' (e.g. <code>nixos-25.11</code>) only provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after the initial release. New stable channels are released every six months.
	** '''Unstable channels''' (e.g. <code>nixos-unstable</code>, <code>nixpkgs-unstable</code>) follow the <code>master</code> branch of Nixpkgs, delivering the latest tested updates on a rolling basis.		** '''Unstable channels''' (e.g. <code>nixos-unstable</code>, <code>nixpkgs-unstable</code>) follow the <code>master</code> branch of Nixpkgs, delivering the latest tested updates on a rolling basis.

	* Large vs small:		* Large vs small:
	** '''Large channels''' (e.g. <code>nixos-25.05</code>, <code>nixos-unstable</code>) are updated only after Hydra has finished building the full breadth of Nixpkgs.		** '''Large channels''' (e.g. <code>nixos-25.11</code>, <code>nixos-unstable</code>) are updated only after Hydra has finished building the full breadth of Nixpkgs.
	** '''Small channels''' (e.g. <code>nixos-25.05-small</code>, <code>nixos-unstable-small</code>) are identical to large channels, but are updated as soon as Hydra has finished building a defined set of commonly-used packages. Thus, users following these channels will get faster updates but may need to build any packages they use from outside the defined set themselves. These channels are intended to be used for server setups, for example.		** '''Small channels''' (e.g. <code>nixos-25.11-small</code>, <code>nixos-unstable-small</code>) are identical to large channels, but are updated as soon as Hydra has finished building a defined set of commonly-used packages. Thus, users following these channels will get faster updates but may need to build any packages they use from outside the defined set themselves. These channels are intended to be used for server setups, for example.

	For most users, a stable/large channel is recommended.		For most users, a stable/large channel is recommended.
Line 52:		Line 52:
	== Using channel branches with flakes ==		== Using channel branches with flakes ==

	Although [[Flakes]] do not make use of traditional Nix channels, they can still reference the same channel branches by specifying them in the flake’s inputs. These branches, such as <code>nixos-25.05</code> or <code>nixos-unstable</code>, correspond to named references within the Nixpkgs repository and serve a similar role in selecting which version of Nixpkgs or other inputs to use.		Although [[Flakes]] do not make use of traditional Nix channels, they can still reference the same channel branches by specifying them in the flake’s inputs. These branches, such as <code>nixos-25.11</code> or <code>nixos-unstable</code>, correspond to named references within the Nixpkgs repository and serve a similar role in selecting which version of Nixpkgs or other inputs to use.

	A simple example of defining channel branches in a flake:		A simple example of defining channel branches in a flake:
Line 59:		Line 59:
	{		{
	inputs = {		inputs = {
	nixpkgs.url = "github:nixos/nixpkgs/nixos-25.05";		nixpkgs.url = "github:nixos/nixpkgs/nixos-25.11";
	nixpkgs-unstable.url = "github:nixos/nixpkgs/nixos-unstable";		nixpkgs-unstable.url = "github:nixos/nixpkgs/nixos-unstable";
	};		};

Hexa: Update jobset names

2025-12-02T00:49:25Z

Update jobset names

← Older revision		Revision as of 00:49, 2 December 2025
Line 76:		Line 76:
	Then, for each '''unstable''' channel (see above), a particular job at [https://hydra.nixos.org hydra.nixos.org] is started which must succeed:		Then, for each '''unstable''' channel (see above), a particular job at [https://hydra.nixos.org hydra.nixos.org] is started which must succeed:

	* For NixOS: the [http://hydra.nixos.org/job/nixos/~~trunk-combined~~/tested ~~trunk-combined~~/tested] job, which includes some automated NixOS tests.		* For NixOS: the [http://hydra.nixos.org/job/nixos/unstable/tested nixos/unstable/tested] job, which includes some automated NixOS tests.
	* For nixos-small: the [http://hydra.nixos.org/job/nixos/unstable-small/tested unstable-small/tested] job.		* For nixos-small: the [http://hydra.nixos.org/job/nixos/unstable-small/tested nixos/unstable-small/tested] job.
	* For nixpkgs: the [http://hydra.nixos.org/job/nixpkgs/~~trunk~~/unstable ~~trunk~~/unstable] job, which contains some critical release packages.		* For nixpkgs: the [http://hydra.nixos.org/job/nixpkgs/unstable/unstable nixpkgs/unstable/unstable] job, which contains some critical release packages.

	=== Success Conditions ===		=== Success Conditions ===

Juancnuno: https://nixos.org/channels redirects to https://channels.nixos.org/

2025-11-08T13:54:32Z

https://nixos.org/channels redirects to https://channels.nixos.org/

← Older revision		Revision as of 13:54, 8 November 2025
Line 28:		Line 28:
	\|-		\|-
	\| Adding a primary channel		\| Adding a primary channel
	\|<code><nowiki>nix-channel --add https://nixos.org~~/channels~~/channel-name nixos</nowiki></code>		\|<code><nowiki>nix-channel --add https://channels.nixos.org/channel-name nixos</nowiki></code>
	\|-		\|-
	\| Adding other channels		\| Adding other channels

Lukec: Reword the first two paragraphs

2025-06-12T20:35:40Z

Reword the first two paragraphs

← Older revision		Revision as of 20:35, 12 June 2025
Line 1:		Line 1:
	Nix channels provide a structured and reliable way to access ~~tested, verified~~ package collections and [[NixOS]] configurations from the [[Nixpkgs]] repository. ~~Rather than installing packages or building systems~~ directly ~~from~~ the frequently updated <code>master</code> branch of Nixpkgs, which receives new commits before extensive testing~~. Because of this~~, ~~users typically follow channel branches.~~		Nix channels provide a structured and reliable way to access package collections and [[NixOS]] configurations from the [[Nixpkgs]] repository. Unlike directly accessing the frequently updated <code>master</code> branch of Nixpkgs which receives new commits before extensive testing, a channel branch is a curated, tested snapshot of Nixpkgs. These branches only advance after builds and tests for a given commit have successfully passed on the [[Hydra]] continuous integration system and are made available via [https://channels.nixos.org channels.nixos.org].

	A channel branch is a curated, tested snapshot of Nixpkgs~~, made available via [https://channels.nixos.org channels.nixos.org]~~. These branches only advance after builds and tests for a given commit have successfully passed on the [[Hydra]] continuous integration system.

	Each channel branch follows a corresponding development branch to which new commits are first added. These new commits are then "verified" using the [[Hydra]] continuous integration system, where each channel branch corresponds to building any new or updated packages for that branch and perform the associated tests. A channel branch is updated once its builds succeeds for a new commit. Contrary to users of the development branches, channel branch users will benefit from both "verified" commits and pre-built packages from the [https://cache.nixos.org official public binary cache].		Each channel branch follows a corresponding development branch to which new commits are first added. These new commits are then "verified" using the [[Hydra]] continuous integration system, where each channel branch corresponds to building any new or updated packages for that branch and perform the associated tests. A channel branch is updated once its builds succeeds for a new commit. Contrary to users of the development branches, channel branch users will benefit from both "verified" commits and pre-built packages from the [https://cache.nixos.org official public binary cache].

Pigs: Reword and reorganize page, add section on flakes and usage in nixos

2025-06-12T17:33:05Z

Reword and reorganize page, add section on flakes and usage in nixos

Show changes

TornaxO7: Update other occurences of `nixos-24.11` to `nixos-25.05`

2025-05-24T10:25:18Z

Update other occurences of `nixos-24.11` to `nixos-25.05`

← Older revision		Revision as of 10:25, 24 May 2025
Line 16:		Line 16:

	* Large/small:		* Large/small:
	** Large channels (<code>nixos-24.11</code>, <code>nixos-unstable</code>) are updated only after Hydra has finished building the full breadth of Nixpkgs.		** Large channels (<code>nixos-25.05</code>, <code>nixos-unstable</code>) are updated only after Hydra has finished building the full breadth of Nixpkgs.
	** Small channels (<code>nixos-24.11-small</code>, <code>nixos-unstable-small</code>) are identical to large channels, but are updated as soon as Hydra has finished building a defined set of commonly-used packages. Thus, users following these channels will get faster updates but may need to build any packages they use from outside the defined set themselves. These channels are intended to be used for server setups, for example.		** Small channels (<code>nixos-25.05-small</code>, <code>nixos-unstable-small</code>) are identical to large channels, but are updated as soon as Hydra has finished building a defined set of commonly-used packages. Thus, users following these channels will get faster updates but may need to build any packages they use from outside the defined set themselves. These channels are intended to be used for server setups, for example.

	Most users will want the stable/large channel, currently <code>nixos-24.11</code>.		Most users will want the stable/large channel, currently <code>nixos-25.05</code>.

	NixOS uses [https://nixos.org/manual/nix/stable/command-ref/files/profiles Nix profiles] for the <code>root</code> user to refer different versions of the system-wide configuration. Profiles set for other users only control the user environment for that user.		NixOS uses [https://nixos.org/manual/nix/stable/command-ref/files/profiles Nix profiles] for the <code>root</code> user to refer different versions of the system-wide configuration. Profiles set for other users only control the user environment for that user.