sublime-merge-dev 0 -> 1
attrpath: sublime-merge-dev
Checking auto update branch...
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] Success
[updateScript] 
Going to be running update for following packages:
 - sublime-merge-2092

Press Enter key to continue...
Running update for:
 - sublime-merge-2092: UPDATING ...
 - sublime-merge-2092: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/applications/version-management/sublime-merge/default.nix b/pkgs/applications/version-management/sublime-merge/default.nix
index 6a1cc1e5575e..07da8f64a6f7 100644
--- a/pkgs/applications/version-management/sublime-merge/default.nix
+++ b/pkgs/applications/version-management/sublime-merge/default.nix
@@ -11,9 +11,9 @@ in
   } { };
 
   sublime-merge-dev = common {
-    buildVersion = "2092";
+    buildVersion = "2094";
     dev = true;
-    aarch64sha256 = "3QMDynXMVB4QVtM8EPbZ8I4m+5sEjzs8XN+jEoMaktM=";
-    x64sha256 = "S9E+wRvO41Eq+PLA/J+sjBIAn6yz715Wg9bKRW2Eobg=";
+    aarch64sha256 = "ZJgq971EPzq+BWxTQAoX6TgUmTfpf9sI4CHPcvgPTfI=";
+    x64sha256 = "6FLfszhP+BGHX5FrycMlznREmGDLyDyo6rgmqxhtCak=";
   } { };
 }

No auto update branch exists
Successfully finished processing
cachix "/nix/store/f2cqcsqf43lgdqli6s0fmfhjq6rxpqmz-sublime-merge-2094"
[check][nixpkgs-review]
Result of `nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>sublime-merge-dev</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from passthru.updateScript.


meta.description for sublime-merge-dev is: Git client from the makers of Sublime Text

meta.homepage for sublime-merge-dev is: https://www.sublimemerge.com




###### Updates performed
- Ran passthru.UpdateScript

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 2094 with grep in /nix/store/f2cqcsqf43lgdqli6s0fmfhjq6rxpqmz-sublime-merge-2094
- found 2094 in filename of file in /nix/store/f2cqcsqf43lgdqli6s0fmfhjq6rxpqmz-sublime-merge-2094

---

<details>
<summary>
<b>Rebuild report</b> (if merged into master) (click to expand)
</summary>

```
1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sublime-merge-dev
```

</details>

<details>
<summary>
<b>Instructions to test this update</b> (click to expand)
</summary>

---

Either **download from Cachix**:
```
nix-store -r /nix/store/f2cqcsqf43lgdqli6s0fmfhjq6rxpqmz-sublime-merge-2094 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '
```
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 sublime-merge-dev https://github.com/r-ryantm/nixpkgs/archive/61d4ab72d5672d21a1e8288c2d1a19b9df29fd5a.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/61d4ab72d5672d21a1e8288c2d1a19b9df29fd5a#sublime-merge-dev
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/f2cqcsqf43lgdqli6s0fmfhjq6rxpqmz-sublime-merge-2094
ls -la /nix/store/f2cqcsqf43lgdqli6s0fmfhjq6rxpqmz-sublime-merge-2094/bin
```

---

</details>
<br/>



### 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.

Result of `nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>sublime-merge-dev</li>
  </ul>
</details>

---

###### Maintainer pings

cc @zookatron for [testing](https://github.com/ryantm/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).
https://api.github.com/repos/NixOS/nixpkgs/pulls/303810