!lZLfSUtSOVjwYTmPbU:nixos.org

nixpkgs-update

185 Members
Keeping nixpkgs up to date. r-ryantm bot. https://github.com/ryantm/nixpkgs-update and https://github.com/nix-community/infra/blob/master/build02/nixpkgs-update.nix56 Servers

Load older messages


SenderMessageTime
11 Jan 2026
@mh0386:matrix.orgMohamed Hisham Abdelzaher joined the room.15:28:56
12 Jan 2026
@magnetophon:matrix.orgmagnetophonThanks. The advantage of a r-ryantm PR is that I can merge it myself.19:34:14
13 Jan 2026
@jopejoe1:matrix.orgjopejoe1 (4094@epvpn) changed their display name from jopejoe1 (4094@39c3) to jopejoe1 (4094@epvpn).08:26:04
14 Jan 2026
@annaaurora:artemislena.eu@annaaurora:artemislena.eu left the room.17:18:21
16 Jan 2026
@mh0386:beeper.comMohamed Hisham Abdelzaher joined the room.13:06:27
17 Jan 2026
@tollb1:matrix.orgtollb1 joined the room.16:58:01
@marcel:envs.net@marcel:envs.net changed their display name from Marcel to Marcel (@).23:44:15
@marcel:envs.net@marcel:envs.net changed their display name from Marcel (@) to Marcel => @me:m4rc3l.de.23:44:59
18 Jan 2026
@marcel:envs.net@marcel:envs.net left the room.17:48:20
19 Jan 2026
@whispers:catgirl.cloudwhispers [& it/fae] joined the room.21:46:55
22 Jan 2026
@thefossguy:matrix.orgPratham Patel joined the room.05:59:10
@thefossguy:matrix.orgPratham Patel

Is it possible to tell the auto-update bot to group commits for a specific set of packages into a single PR? At the moment, auto-updates for COSMIC packages are turned off and I "manually" auto-update them with the following command on my local machine and then creating a PR:

nix-shell maintainers/scripts/update.nix \
    --argstr commit true \
    --argstr keep-going true \
    --argstr max-workers 1 \
    --argstr skip-prompt true \
    --arg predicate '(path: pkg: let lib = import <nixpkgs/lib>; in lib.lists.elem lib.teams.cosmic (pkg.meta.teams or []))'

I was wondering if this could be automated in such a way that all package update commits are in a single PR. This is because upstream tags new versions for all stable packages at once, meaning we update all stable packages with each new release. But the motivating factor for automating this is that upstream is switching to weekly releases. I'd much rather spend my time on reviewing and let the auto-update bot handle updates, if possible.

I have given this some thought and am thinking of creating these two files in nixpkgs:

# pkgs/by-name/co/cosmic-packages-upgrade-script/package.nix
{
  stdenvNoCC,
  writeShellScript,
  lib,
}:

stdenvNoCC.mkDerivation {
  name = "cosmic-packages-upgrade-script";

  passthru.updateScript = import ./update-script.nix { inherit writeShellScript; };

  meta = {
    description = "A package to auto-upgrade all COSMIC packages maintained by the nixpkgs COSMIC team";
    license = lib.licenses.mit;
    teams = [ lib.teams.cosmic ];
    platforms = lib.platforms.linux;
  };
}
# pkgs/by-name/co/cosmic-packages-upgrade-script/update-script.nix
{ writeShellScript }:

writeShellScript "cosmic-packages-upgrade-script" ''
  cd "$(git rev-parse --show-toplevel)" || exit 1
  exec nix-shell maintainers/scripts/update.nix \
    --argstr commit true \
    --argstr keep-going true \
    --argstr max-workers 1 \
    --argstr skip-prompt true \
    --arg predicate '(path: pkg: let lib = import <nixpkgs/lib>; in lib.lists.elem lib.teams.cosmic (pkg.meta.teams or []))'
''

Is this cursed? Would it even work? What's the recommended method here?

06:09:00
@gus:gu5.orgGus left the room.15:35:27
23 Jan 2026
@nivayu:matrix.orgNivayu joined the room.16:03:38
@voxel:nyanbinary.rsluna 🏳️‍⚧️ set a profile picture.21:18:36
27 Jan 2026
@whispers:catgirl.cloudwhispers [& it/fae] changed their display name from whispers (it/fae) to whispers [& it/fae].02:51:38
28 Jan 2026
@mlyx:matrix.orgmlyx joined the room.05:22:14
1 Feb 2026
@sigmasquadron:matrix.orgFernando Rodrigues changed their display name from SigmaSquadron to Fernando Rodrigues.10:42:51
2 Feb 2026
@sersorrel:matrix.org@sersorrel:matrix.org left the room.00:50:10
@mdaniels5757:matrix.orgmdaniels5757 joined the room.02:40:31

There are no newer messages yet.


Back to Room ListRoom Version: 9