Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: equicord 2026-01-19 -> 2026-02-16 https://github.com/Equicord/Equicord/releases
attrpath: equicord
Checking auto update branch...
[version]
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion]
[rustCrateVersion] No cargoHash found
[golangModuleVersion]
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion]
[npmDepsVersion] No npmDepsHash
[updateScript]
[updateScript] Success
[updateScript] this derivation will be built:
/nix/store/ijdga0hdjg3q1mdqb3138mb6v4qr0j01-packages.json.drv
building '/nix/store/ijdga0hdjg3q1mdqb3138mb6v4qr0j01-packages.json.drv'...
Going to be running update for following packages:
- equicord-2026-01-19
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- equicord-2026-01-19: UPDATING ...
- equicord-2026-01-19: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/eq/equicord/package.nix b/pkgs/by-name/eq/equicord/package.nix
index 60947666ec93..b76075a42f1b 100644
--- a/pkgs/by-name/eq/equicord/package.nix
+++ b/pkgs/by-name/eq/equicord/package.nix
@@ -20,20 +20,20 @@ stdenv.mkDerivation (finalAttrs: {
# the Equicord repository. Dates as tags (and automatic releases) were the compromise
# we came to with upstream. Please do not change the version schema (e.g., to semver)
# unless upstream changes the tag schema from dates.
- version = "2026-01-19";
+ version = "2026-02-16";
src = fetchFromGitHub {
owner = "Equicord";
repo = "Equicord";
tag = finalAttrs.version;
- hash = "sha256-pEFU1E+BqAAAz2ywPrS1MejhZ/g47iG/4BBey+2F7Hw=";
+ hash = "sha256-YSTLO2DtUWNfTpUMjtFjVOAt8jOnAxZnfZFFFXe7Fkg=";
};
pnpmDeps = fetchPnpmDeps {
inherit (finalAttrs) pname version src;
pnpm = pnpm_10;
fetcherVersion = 1;
- hash = "sha256-iBCA4G1E1Yw/d94pQzcbBGJYeIIgZI+Gw87/x4ogoyg=";
+ hash = "sha256-um8CmR4H+sck6sOpIpnISPhYn/rvXNfSn6i/EgQFvk0=";
};
nativeBuildInputs = [
An auto update branch exists with message `equicord: 2026-01-19 -> 2026-02-08`. New version is 2026-02-16.
The auto update branch does not match or exceed the new version.
Successfully finished processing
[check][nixpkgs-review]
## `nixpkgs-review` result
Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).
Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `cc2e1820a7c20e79685c0ac9f8b38750dc4b3b73`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from passthru.updateScript.
meta.description for equicord is: Other cutest Discord client mod
meta.homepage for equicord is: https://github.com/Equicord/Equicord
###### Updates performed
- Ran passthru.UpdateScript
###### To inspect upstream changes
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 2026-02-16 with grep in /nix/store/2m5qfs2qjlsasla2z994lyys53amfq5k-equicord-2026-02-16
- found 2026-02-16 in filename of file in /nix/store/2m5qfs2qjlsasla2z994lyys53amfq5k-equicord-2026-02-16
---
Rebuild report (if merged into master) (click to expand)
```
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
equicord
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/2m5qfs2qjlsasla2z994lyys53amfq5k-equicord-2026-02-16 \
--option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
--option trusted-public-keys '
nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
'
```
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted.
Or, **build yourself**:
```
nix-build -A equicord https://github.com/r-ryantm/nixpkgs/archive/cc2e1820a7c20e79685c0ac9f8b38750dc4b3b73.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/cc2e1820a7c20e79685c0ac9f8b38750dc4b3b73#equicord
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/2m5qfs2qjlsasla2z994lyys53amfq5k-equicord-2026-02-16
ls -la /nix/store/2m5qfs2qjlsasla2z994lyys53amfq5k-equicord-2026-02-16/bin
```
---
### Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as _failed to build_ independent of the
change, simply because they are already broken on the target branch.
## `nixpkgs-review` result
Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).
Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `cc2e1820a7c20e79685c0ac9f8b38750dc4b3b73`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
---
###### Maintainer pings
cc @NotAShelf for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).
> [!TIP]
> As a maintainer, if your package is located under `pkgs/by-name/*`, you can comment **`@NixOS/nixpkgs-merge-bot merge`** to automatically merge this update using the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot).
Updated existing PR
https://api.github.com/repos/NixOS/nixpkgs/pulls/483768