Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: atuin 18.10.0 -> 18.11.0 https://github.com/atuinsh/atuin/releases
attrpath: atuin
Checking auto update branch...
[version]
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion]
[rustCrateVersion] skipping because derivation has updateScript
[golangModuleVersion]
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion]
[npmDepsVersion] No npmDepsHash
[updateScript]
[updateScript] Success
[updateScript]
Going to be running update for following packages:
- atuin-18.10.0
Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
- atuin-18.10.0: UPDATING ...
- atuin-18.10.0: DONE.
Packages updated!
Diff after rewrites:
diff --git a/pkgs/by-name/at/atuin/package.nix b/pkgs/by-name/at/atuin/package.nix
index be7053870fca..a55c5cad8a49 100644
--- a/pkgs/by-name/at/atuin/package.nix
+++ b/pkgs/by-name/at/atuin/package.nix
@@ -10,16 +10,16 @@
rustPlatform.buildRustPackage (finalAttrs: {
pname = "atuin";
- version = "18.10.0";
+ version = "18.11.0";
src = fetchFromGitHub {
owner = "atuinsh";
repo = "atuin";
tag = "v${finalAttrs.version}";
- hash = "sha256-bfSa3RtVXxHt3usDqqpE/oXKKDUZOrf+tD9uL59fr6M=";
+ hash = "sha256-yjsCNN15E06te6cueSZksg7mcMyx2FiXKrbGAEcQWmg=";
};
- cargoHash = "sha256-67ffivZVCly1GWA3fJ9mT8nGv2EGd6eCthbaIu/IW3M=";
+ cargoHash = "sha256-xaALIVJpMek4nbSozxtOEWivRDlMmKdu6KqKiNMp0jk=";
# atuin's default features include 'check-updates', which do not make sense
# for distribution builds. List all other default features.
No auto update branch exists
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: `171403d1e32a58d35eabb399f8e8c97b415e0cee`
---
### `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 atuin is: Replacement for a shell history which records additional commands context with optional encrypted synchronization between machines
meta.homepage for atuin is: https://github.com/atuinsh/atuin
###### 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 18.11.0 with grep in /nix/store/d7w35fr11i2dbhaa0lwn6hkiyk2h0001-atuin-18.11.0
- found 18.11.0 in filename of file in /nix/store/d7w35fr11i2dbhaa0lwn6hkiyk2h0001-atuin-18.11.0
---
Rebuild report (if merged into master) (click to expand)
```
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
atuin
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/d7w35fr11i2dbhaa0lwn6hkiyk2h0001-atuin-18.11.0 \
--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 atuin https://github.com/r-ryantm/nixpkgs/archive/171403d1e32a58d35eabb399f8e8c97b415e0cee.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/171403d1e32a58d35eabb399f8e8c97b415e0cee#atuin
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/d7w35fr11i2dbhaa0lwn6hkiyk2h0001-atuin-18.11.0
ls -la /nix/store/d7w35fr11i2dbhaa0lwn6hkiyk2h0001-atuin-18.11.0/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: `171403d1e32a58d35eabb399f8e8c97b415e0cee`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
---
###### Maintainer pings
cc @SuperSandro2000 @Sciencentistguy @0x4A6F @R-VdP 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).
---
Add a :+1: [reaction] to [pull requests you find important].
[reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/
[pull requests you find important]: https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+sort%3Areactions-%2B1-desc
https://api.github.com/repos/NixOS/nixpkgs/pulls/480154