-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
zarf: 0.57.0 -> 0.61.0 #424564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
zarf: 0.57.0 -> 0.61.0 #424564
Conversation
|
e86c0f7
to
426d458
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zarf-dev/zarf/releases. meta.description for zarf is: DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev meta.homepage for zarf is: https://zarf.dev Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zarf-dev/zarf/releases. meta.description for zarf is: DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev meta.homepage for zarf is: https://zarf.dev Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
426d458
to
3165c67
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zarf-dev/zarf/releases. meta.description for zarf is: DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev meta.homepage for zarf is: https://zarf.dev Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)Either download from the cache:
(The nixpkgs-update cache is only trusted for this store-path realization.) Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages.
|
3165c67
to
1294ab4
Compare
postInstall needs to be disabled for Darwin |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zarf-dev/zarf/releases.
meta.description for zarf is: DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev
meta.homepage for zarf is: https://zarf.dev
Updates performed
To inspect upstream changes
Impact
Checks done
passthru.tests
, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from the cache:
(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 usesudo
since root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
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
resultGenerated using
nixpkgs-review
.Command:
nixpkgs-review
x86_64-linux
✅ 1 package built:
Maintainer pings
cc @ragingpastry for testing.
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 thenixpkgs-merge-bot
.Add a 👍 reaction to pull requests you find important.