-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
kops: 1.29.2 -> 1.33.0 #349947
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?
kops: 1.29.2 -> 1.33.0 #349947
Conversation
This is just updating the 1.29 release to be the same as the 1.30 release. Seems someone should remove the update script from this package unless there's an easy way to fix. IIRC, the only way to stop auto-update from just doing this again is to leave this open as a draft. |
Is it the case that if we leave this in draft that @r-ryantm won't try to re-open it? |
f88c9b6
to
8758cd9
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kops/releases. meta.description for kops is: Easiest way to get a production Kubernetes up and running meta.homepage for kops is: https://github.com/kubernetes/kops meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases 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 Cachix:
(The Cachix 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.
|
8758cd9
to
d4e3647
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kops/releases. meta.description for kops is: Easiest way to get a production Kubernetes up and running meta.homepage for kops is: https://github.com/kubernetes/kops meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases 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 Cachix:
(The Cachix 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.
|
d4e3647
to
a055266
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kops/releases. meta.description for kops is: Easiest way to get a production Kubernetes up and running meta.homepage for kops is: https://github.com/kubernetes/kops meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases 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.
|
@ryantm, (how) can we correct this behaviour? |
a055266
to
32021a4
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kops/releases. meta.description for kops is: Easiest way to get a production Kubernetes up and running meta.homepage for kops is: https://github.com/kubernetes/kops meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases 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.
|
32021a4
to
0368ce3
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kops/releases. meta.description for kops is: Easiest way to get a production Kubernetes up and running meta.homepage for kops is: https://github.com/kubernetes/kops meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases 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.
|
0368ce3
to
d23af4c
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kops/releases. meta.description for kops is: Easiest way to get a production Kubernetes up and running meta.homepage for kops is: https://github.com/kubernetes/kops meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases 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/kubernetes/kops/releases.
meta.description for kops is: Easiest way to get a production Kubernetes up and running
meta.homepage for kops is: https://github.com/kubernetes/kops
meta.changelog for kops is: https://github.com/kubernetes/kops/tree/master/docs/releases
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
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 Cachix:
(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 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 @offlinehacker @zimbatm @DiegoLelis @yurrriq 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.