-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
cargo-about: 0.6.6 -> 0.7.1 #392011
cargo-about: 0.6.6 -> 0.7.1 #392011
Conversation
@NixOS/nixpkgs-merge-bot merge |
Merge completed (#306934) |
I think this might've broken zed-editor |
Indeed:
|
It even said so in the PR description so I'm not sure why @matthiasbeyer merged it right away. Also it would be helpful if r-ryantm pinged maintainers of affected packages. 🤔 |
Because I totally missed that part. Sorry about that!
Yep, that would indeed be helpful, at least for packages that get broken! |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/EmbarkStudios/cargo-about/releases.
meta.description for cargo-about is: Cargo plugin to generate list of all licenses for a crate
meta.homepage for cargo-about is: https://github.com/EmbarkStudios/cargo-about
meta.changelog for cargo-about is: https://github.com/EmbarkStudios/cargo-about/blob/0.7.1/CHANGELOG.md
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 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
❌ 3 packages failed to build:
✅ 3 packages built:
Maintainer pings
cc @evanjs @figsoda @matthiasbeyer 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.