Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cargo-expand: 0.4.10 -> 0.4.11 #59917

Merged
merged 1 commit into from Apr 20, 2019
Merged

cargo-expand: 0.4.10 -> 0.4.11 #59917

merged 1 commit into from Apr 20, 2019

Conversation

xrelkd
Copy link
Contributor

@xrelkd xrelkd commented Apr 20, 2019

Motivation for this change

Update cargo-expand to the latest release.

https://github.com/dtolnay/cargo-expand/releases/tag/0.4.11

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@dywedir
Copy link
Member

dywedir commented Apr 20, 2019

@GrahamcOfBorg build cargo-expand

@dywedir dywedir merged commit b8243d1 into NixOS:master Apr 20, 2019
@xrelkd xrelkd deleted the update/cargo-expand branch April 20, 2019 10:00
@xrelkd
Copy link
Contributor Author

xrelkd commented Apr 20, 2019

@dywedir, thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
10.rebuild-darwin: 1-10 10.rebuild-linux: 1-10 11.by: package-maintainer
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@xrelkd @dywedir @GrahamcOfBorg