Skip to content

Conversation

@r-ryantm
Copy link
Contributor

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/googleapis/api-linter/releases.

meta.description for api-linter is: Linter for APIs defined in protocol buffers

meta.homepage for api-linter is: https://github.com/googleapis/api-linter/

meta.changelog for api-linter is: https://github.com/googleapis/api-linter/releases/tag/refs/tags/v2.0.0

Updates performed
  • Golang update
To inspect upstream changes
Impact

Checks done


  • built on NixOS
  • The tests defined in passthru.tests, if any, passed
  • found 2.0.0 with grep in /nix/store/qv6839x91vjckfpnmkhkp1hr6pk1zps6-api-linter-2.0.0
  • found 2.0.0 in filename of file in /nix/store/qv6839x91vjckfpnmkhkp1hr6pk1zps6-api-linter-2.0.0

Rebuild report (if merged into master) (click to expand)
2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

api-linter
Instructions to test this update (click to expand)

Either download from the cache:

nix-store -r /nix/store/qv6839x91vjckfpnmkhkp1hr6pk1zps6-api-linter-2.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(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 use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A api-linter https://github.com/r-ryantm/nixpkgs/archive/338fbbb6d6c21d0e33473a98c6dc7ce1f8759e5b.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/338fbbb6d6c21d0e33473a98c6dc7ce1f8759e5b#api-linter

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/qv6839x91vjckfpnmkhkp1hr6pk1zps6-api-linter-2.0.0
ls -la /nix/store/qv6839x91vjckfpnmkhkp1hr6pk1zps6-api-linter-2.0.0/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.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: 338fbbb6d6c21d0e33473a98c6dc7ce1f8759e5b


x86_64-linux

✅ 1 package built:
  • api-linter

Maintainer pings

cc @xrelkd 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 the nixpkgs-merge-bot.


Add a 👍 reaction to pull requests you find important.

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. labels Oct 28, 2025
@nix-owners nix-owners bot requested a review from xrelkd October 28, 2025 04:25
@nixpkgs-ci nixpkgs-ci bot added 9.needs: reviewer This PR currently has no reviewers requested and needs attention. and removed 9.needs: reviewer This PR currently has no reviewers requested and needs attention. labels Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant