fulcio 1.4.3 -> 1.4.4 https://github.com/sigstore/fulcio/releases
attrpath: fulcio
Checking auto update branch...
No auto update branch exists
[version]
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion]
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion]
[golangModuleVersion] Found old vendorHash = "sha256-ImZJXdOfMepMFU1z47XyNU39NGGdiCzQji2/tKVfibQ="
[golangModuleVersion] Replaced vendorHash with sha256-B4/SIY9G5uEP+P+oSdhaMM7HRaHm5nq2jqXdIWxdP+8=
[golangModuleVersion] Finished updating vendorHash
[npmDepsVersion]
[npmDepsVersion] No npmDepsHash
[updateScript]
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/tools/security/fulcio/default.nix b/pkgs/tools/security/fulcio/default.nix
index 9c40c051bebc..17bd273c0a30 100644
--- a/pkgs/tools/security/fulcio/default.nix
+++ b/pkgs/tools/security/fulcio/default.nix
@@ -2,13 +2,13 @@
buildGoModule rec {
pname = "fulcio";
- version = "1.4.3";
+ version = "1.4.4";
src = fetchFromGitHub {
owner = "sigstore";
repo = pname;
rev = "v${version}";
- sha256 = "sha256-LT8J9s008XQtDtNdH1ungQREqQUrlTsoxnlRLKimqLY=";
+ sha256 = "sha256-zL+53GIGDQagWtsSHQT1Gn1hZUCpYF3uYKXmJWFGy7k=";
# populate values that require us to use git. By doing this in postFetch we
# can delete .git afterwards and maintain better reproducibility of the src.
leaveDotGit = true;
@@ -20,7 +20,7 @@ buildGoModule rec {
find "$out" -name .git -print0 | xargs -0 rm -rf
'';
};
- vendorHash = "sha256-ImZJXdOfMepMFU1z47XyNU39NGGdiCzQji2/tKVfibQ=";
+ vendorHash = "sha256-B4/SIY9G5uEP+P+oSdhaMM7HRaHm5nq2jqXdIWxdP+8=";
nativeBuildInputs = [ installShellFiles ];
Successfully finished processing
cachix "/nix/store/a5jzjnk6gz3kzn0zsqy0gcmlm39zqkh3-fulcio-1.4.4"
[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)
1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/sigstore/fulcio/releases.
meta.description for fulcio is: A Root-CA for code signing certs - issuing certificates based on an OIDC email address
meta.homepage for fulcio is: https://github.com/sigstore/fulcio
meta.changelog for fulcio is: https://github.com/sigstore/fulcio/releases/tag/v1.4.4
###### Updates performed
- Golang update
###### To inspect upstream changes
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 1.4.4 with grep in /nix/store/a5jzjnk6gz3kzn0zsqy0gcmlm39zqkh3-fulcio-1.4.4
- found 1.4.4 in filename of file in /nix/store/a5jzjnk6gz3kzn0zsqy0gcmlm39zqkh3-fulcio-1.4.4
---
Rebuild report (if merged into master) (click to expand)
```
1 total rebuild path(s)
1 package rebuild(s)
First fifty rebuilds by attrpath
fulcio
```
Instructions to test this update (click to expand)
---
Either **download from Cachix**:
```
nix-store -r /nix/store/a5jzjnk6gz3kzn0zsqy0gcmlm39zqkh3-fulcio-1.4.4 \
--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 fulcio https://github.com/r-ryantm/nixpkgs/archive/7a11e15a39e2caec122cd7bed91f98c85d0874cb.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/7a11e15a39e2caec122cd7bed91f98c85d0874cb#fulcio
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/a5jzjnk6gz3kzn0zsqy0gcmlm39zqkh3-fulcio-1.4.4
ls -la /nix/store/a5jzjnk6gz3kzn0zsqy0gcmlm39zqkh3-fulcio-1.4.4/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.
Result of `nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
---
###### Maintainer pings
cc @LeSuisse @06kellyjac 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/292218