Nixpkgs/Automatic Updates - Revision history

SarahClark: /* A special note for Python Monorepos */ fix case

2026-07-24T17:58:22Z

A special note for Python Monorepos: fix case

← Older revision		Revision as of 17:58, 24 July 2026
Line 77:		Line 77:
	The git updaters also look at a limited window of changes. You still need to verify periodically that your package has updated to the latest version and make the edits by hand if it's behind.		The git updaters also look at a limited window of changes. You still need to verify periodically that your package has updated to the latest version and make the edits by hand if it's behind.

	=== A special note for Python ~~Monorepos~~ ===		=== A special note for Python monorepos ===
	The committers run a fast bulk python update script several times a year. This script ignores <code>passthru.updateScript</code> and use the latest git tag. That often breaks monorepo-based packages by setting the wrong <code>src.version</code> expression and/or version number.		The committers run a fast bulk python update script several times a year. This script ignores <code>passthru.updateScript</code> and use the latest git tag. That often breaks monorepo-based packages by setting the wrong <code>src.version</code> expression and/or version number.

SarahClark: fix typo

2026-07-24T17:57:56Z

fix typo

← Older revision		Revision as of 17:57, 24 July 2026
Line 75:		Line 75:
	Updates can fail with "no matching tag found" when the repo pushes out a large number of packages. <code>nix-update-script</code> examines approximately the last 20 releases. In this case, you can switch to the git updater with <code>rev-prefix</code>.		Updates can fail with "no matching tag found" when the repo pushes out a large number of packages. <code>nix-update-script</code> examines approximately the last 20 releases. In this case, you can switch to the git updater with <code>rev-prefix</code>.

	The git updaters also look at a limited window of changes. You still need to verify periodically that your package has updated to the latest version and make the edits by hand is it's behind.		The git updaters also look at a limited window of changes. You still need to verify periodically that your package has updated to the latest version and make the edits by hand if it's behind.

	=== A special note for Python Monorepos ===		=== A special note for Python Monorepos ===

SarahClark: Added advice for maintaining monorepos and a special precaution for Python monorepos.

2026-07-24T17:57:09Z

Added advice for maintaining monorepos and a special precaution for Python monorepos.

@@ Line 68: / Line 68: @@
 };
 </syntaxhighlight>Source: https://github.com/NixOS/nixpkgs/blob/master/pkgs/common-updater/unstable-updater.nix
 == Additional Resources ==

SarahClark: /* nix-update by Mic92 */ Documented --version-regex including its quirks

2026-07-24T17:30:02Z

nix-update by Mic92: Documented --version-regex including its quirks

← Older revision		Revision as of 17:30, 24 July 2026
Line 28:		Line 28:
	If you want functionality similar to that of unstableGitUpdater but with the additional handlers offered by nix-update, use:		If you want functionality similar to that of unstableGitUpdater but with the additional handlers offered by nix-update, use:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">passthru.updateScript = nix-update-script { extraArgs = [ "--version=branch" ]; };</syntaxhighlight>
	passthru.updateScript = nix-update-script { extraArgs = [ "--version=~~branch~~" ]; };
	</syntaxhighlight>		==== Setting a custom for prefixed releases ====
			<code>nix-updater</code> expects an all-numeric version such as <code>1.2.3</code> and fails when there's a prefix (<code>v1.2.3</code>). When that happens, you'll need to set a custom regex:<syntaxhighlight lang="nix">
			passthru.updateScript = nix-update-script {
			extraArgs = [ "--version-regex=v([\\d.]+)" ];
			};

			</syntaxhighlight>Note there's only one capturing group (in parentheses). Due to a quirk in the updater, nesting capturing groups won't give the results you expect. The regex implicitly matches the whole line.

	=== Git Updater ===		=== Git Updater ===

Pandapip1: Minor grammar/formatting

2026-03-05T23:27:33Z

Minor grammar/formatting

← Older revision		Revision as of 23:27, 5 March 2026
Line 1:		Line 1:
	[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]).<br />		[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]).<br />
	It uses package repository information from Repology.org (though that requires other projects to detect the update), the GitHub releases API, and - if available - the package <code>passthru.updateScript</code>. For more information, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].		It uses package repository information from Repology.org (though that requires other projects to detect the update), the GitHub releases API, and, if available, the package <code>passthru.updateScript</code>. For more information, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].

	If you're wondering why your package isn't receiving automated updates, it can be useful to check the [https://r.ryantm.com/log/ r-ryantm logs].		If you're wondering why your package isn't receiving automated updates, it can be useful to check the [https://r.ryantm.com/log/ r-ryantm logs].

Tbertels: formatting

2026-03-05T13:52:35Z

formatting

← Older revision		Revision as of 13:52, 5 March 2026
Line 1:		Line 1:
	[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]).		[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]).<br />
	It uses package repository information from Repology.org (though that requires other projects to detect the update), the GitHub releases API, and - if available - the package <code>passthru.updateScript</code>. For more information, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].		It uses package repository information from Repology.org (though that requires other projects to detect the update), the GitHub releases API, and - if available - the package <code>passthru.updateScript</code>. For more information, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].

Tbertels: corr: nixpkgs-update is always used by r-ryantm, +information about how it works

2026-03-05T13:52:00Z

corr: nixpkgs-update is always used by r-ryantm, +information about how it works

← Older revision		Revision as of 13:52, 5 March 2026
Line 1:		Line 1:
	[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]), if the package ~~does not specify an~~ <code>updateScript</code>. For more ~~info~~, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].		[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]).
			It uses package repository information from Repology.org (though that requires other projects to detect the update), the GitHub releases API, and - if available - the package <code>passthru.updateScript</code>. For more information, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].

	If you're wondering why your package isn't receiving automated updates, it can be useful to check the [https://r.ryantm.com/log/ r-ryantm logs].		If you're wondering why your package isn't receiving automated updates, it can be useful to check the [https://r.ryantm.com/log/ r-ryantm logs].

Tbertels: /* Additional Resources */ +R. RyanTM nixpkgs-update bot information link

2026-01-15T11:42:52Z

Additional Resources: +R. RyanTM nixpkgs-update bot information link

← Older revision		Revision as of 11:42, 15 January 2026
Line 65:		Line 65:

	* [https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#automatic-package-updates Contributing to nixpkgs - Automatic Package Updates (github.com/nixos/nixpkgs)]		* [https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#automatic-package-updates Contributing to nixpkgs - Automatic Package Updates (github.com/nixos/nixpkgs)]
			* [https://nix-community.org/update-bot/ R. RyanTM nixpkgs-update bot information]

	[[Category:Nixpkgs]]		[[Category:Nixpkgs]]

Tbertels: section level

2026-01-15T11:09:13Z

section level

← Older revision		Revision as of 11:09, 15 January 2026
Line 3:		Line 3:
	If you're wondering why your package isn't receiving automated updates, it can be useful to check the [https://r.ryantm.com/log/ r-ryantm logs].		If you're wondering why your package isn't receiving automated updates, it can be useful to check the [https://r.ryantm.com/log/ r-ryantm logs].

	=== Disabling nixpkgs-update for individual packages ===		== Disabling nixpkgs-update for individual packages ==

	Put the following comment somewhere in the package file:		Put the following comment somewhere in the package file:

Tbertels: Move Automatic updates with r-ryantm > nixpkgs-update to the lead as it's the standard behavior

2026-01-15T11:06:15Z

Move Automatic updates with r-ryantm > nixpkgs-update to the lead as it's the standard behavior

@@ Line 1: / Line 1: @@
-Update Scripts can be added to packages by setting <code><nowiki>passthru.updateScript</nowiki></code>. This is then executed by [[r-ryantm]] to create an updated pull request. It can be manually invoked via <code>nix-shell maintainers/scripts/update.nix --argstr package <packagename></code>.
+[https://github.com/nix-community/nixpkgs-update nixpkgs-update] is used by [[r-ryantm]] for automated updates (through creating [https://github.com/NixOS/nixpkgs/issues?q=is%3Apr%20author%3Ar-ryantm update pull requests]), if the package does not specify an <code>updateScript</code>. For more info, see the [https://nix-community.github.io/nixpkgs-update/ official documentation].
 == Update Scripts ==
-List of prepackaged update scripts.
 === nix-update by Mic92 ===
 [https://github.com/Mic92/nix-update nix-update] works for a range of different sources and will do the right thing most of the time.
@@ Line 47: / Line 61: @@
 };
 </syntaxhighlight>Source: https://github.com/NixOS/nixpkgs/blob/master/pkgs/common-updater/unstable-updater.nix
 == Additional Resources ==