nghttp3 0.10.0 -> 0.11.0 https://repology.org/project/nghttp3/versions
attrpath: nghttp3
Checking auto update branch...
No auto update branch exists
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript

[quotedUrls]
[quotedUrls] nothing found to replace
Diff after rewrites:
diff --git a/pkgs/development/libraries/nghttp3/default.nix b/pkgs/development/libraries/nghttp3/default.nix
index e7d57d457bd..38e996330e7 100644
--- a/pkgs/development/libraries/nghttp3/default.nix
+++ b/pkgs/development/libraries/nghttp3/default.nix
@@ -6,13 +6,13 @@
 
 stdenv.mkDerivation rec {
   pname = "nghttp3";
-  version = "0.10.0";
+  version = "0.11.0";
 
   src = fetchFromGitHub {
     owner = "ngtcp2";
     repo = pname;
     rev = "v${version}";
-    hash = "sha256-V0g/d1B9uMn7KZU6ShzyPGXOSAYCbz4ZubnhAwz+Qsc=";
+    hash = "sha256-fZMFSQ8RCVxuoLrisa8lLqjNVe4fIuGqbyKtkC/u02M=";
   };
 
   outputs = [ "out" "dev" "doc" ];

Successfully finished processing
cachix "/nix/store/c7793ry6mnlnip1439c0gpvf1zxqyrvh-nghttp3-0.11.0"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>2 packages failed to build:</summary>
  <ul>
    <li>curlHTTP3</li>
    <li>ngtcp2</li>
  </ul>
</details>
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>nghttp3</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/nghttp3/versions.


meta.description for nghttp3 is: nghttp3 is an implementation of HTTP/3 mapping over QUIC and QPACK in C.

meta.homepage for nghttp3 is: https://github.com/ngtcp2/nghttp3




###### Updates performed
- Version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/ngtcp2/nghttp3/releases/tag/v0.11.0)

- [Compare changes on GitHub](https://github.com/ngtcp2/nghttp3/compare/v0.10.0...v0.11.0)

###### Impact

<details>
<summary>
<b>Checks done</b> (click to expand)
</summary>

---

- built on NixOS
- Warning: a test defined in `passthru.tests` did not pass
- found 0.11.0 with grep in /nix/store/c7793ry6mnlnip1439c0gpvf1zxqyrvh-nghttp3-0.11.0
- found 0.11.0 in filename of file in /nix/store/c7793ry6mnlnip1439c0gpvf1zxqyrvh-nghttp3-0.11.0

---

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

```
3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
curlHTTP3
nghttp3
ngtcp2
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/c7793ry6mnlnip1439c0gpvf1zxqyrvh-nghttp3-0.11.0 \
  --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 nghttp3 https://github.com/r-ryantm/nixpkgs/archive/5c8117414a98a71b4d73ec85466c86c809e70dc4.tar.gz
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/c7793ry6mnlnip1439c0gpvf1zxqyrvh-nghttp3-0.11.0
ls -la /nix/store/c7793ry6mnlnip1439c0gpvf1zxqyrvh-nghttp3-0.11.0/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` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>2 packages failed to build:</summary>
  <ul>
    <li>curlHTTP3</li>
    <li>ngtcp2</li>
  </ul>
</details>
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>nghttp3</li>
  </ul>
</details>

---

###### Maintainer pings

cc @Izorkin for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/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/228884