clang-tidy-sarif 0 -> 1 attrpath: clang-tidy-sarif Checking auto update branch... [version] [version] generic version rewriter does not support multiple hashes [rustCrateVersion] [rustCrateVersion] skipping because derivation has updateScript [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] Success [updateScript] this derivation will be built: /nix/store/j5q9k6w2w7fwyxqh2ibd3zj5l7gnpfri-packages.json.drv building '/nix/store/j5q9k6w2w7fwyxqh2ibd3zj5l7gnpfri-packages.json.drv'... Going to be running update for following packages: - clang-tidy-sarif-0.6.5 Press Enter key to continue... Running update for: - clang-tidy-sarif-0.6.5: UPDATING ... - clang-tidy-sarif-0.6.5: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/cl/clang-tidy-sarif/package.nix b/pkgs/by-name/cl/clang-tidy-sarif/package.nix index 4dce159eedd5..01a2c1bcfd5e 100644 --- a/pkgs/by-name/cl/clang-tidy-sarif/package.nix +++ b/pkgs/by-name/cl/clang-tidy-sarif/package.nix @@ -7,14 +7,14 @@ }: rustPlatform.buildRustPackage rec { pname = "clang-tidy-sarif"; - version = "0.6.5"; + version = "0.6.6"; src = fetchCrate { inherit pname version; - hash = "sha256-pQbhLbDRcZJhXXY6bWGO/8mmQRwgM3tDEWKoqmsNr68="; + hash = "sha256-rZnGueaqK7h8tWwwWacvFBvJwE1li2wN9iB4DJRHJ8U="; }; - cargoHash = "sha256-K+Cle2eCH4jCLbYfOrlEXeBvFUr7dGmpKFQM1IJi7p4="; + cargoHash = "sha256-mELx6UGHV+qtL1G3+xvYUaUzZbfMy0dKgai6IqdbT+A="; nativeInstallCheckInputs = [ versionCheckHook ]; doInstallCheck = true; No auto update branch exists Successfully finished processing cachix "/nix/store/l3j3xiqcka1395zb905mbq9sn9gxc8wv-clang-tidy-sarif-0.6.6" [check][nixpkgs-review] Result of `nixpkgs-review` 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 passthru.updateScript. meta.description for clang-tidy-sarif is: A CLI tool to convert clang-tidy diagnostics into SARIF meta.homepage for clang-tidy-sarif is: https://psastras.github.io/sarif-rs ###### Updates performed - Ran passthru.UpdateScript ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 0.6.6 with grep in /nix/store/l3j3xiqcka1395zb905mbq9sn9gxc8wv-clang-tidy-sarif-0.6.6 - found 0.6.6 in filename of file in /nix/store/l3j3xiqcka1395zb905mbq9sn9gxc8wv-clang-tidy-sarif-0.6.6 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath clang-tidy-sarif ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/l3j3xiqcka1395zb905mbq9sn9gxc8wv-clang-tidy-sarif-0.6.6 \ --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 clang-tidy-sarif https://github.com/r-ryantm/nixpkgs/archive/2379f18590b3e26b6d6bb6d34fea72b10b4c42e5.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/2379f18590b3e26b6d6bb6d34fea72b10b4c42e5#clang-tidy-sarif ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/l3j3xiqcka1395zb905mbq9sn9gxc8wv-clang-tidy-sarif-0.6.6 ls -la /nix/store/l3j3xiqcka1395zb905mbq9sn9gxc8wv-clang-tidy-sarif-0.6.6/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` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
--- ###### Maintainer pings cc @getchoo for [testing](https://github.com/ryantm/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). > [!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 the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs-merge-bot). --- Add a :+1: [reaction] to [pull requests you find important]. [reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/ [pull requests you find important]: https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+sort%3Areactions-%2B1-desc https://api.github.com/repos/NixOS/nixpkgs/pulls/339191