go-mockery: 2.52.1 -> 2.53.2, terragrunt: 0.75.10 -> 0.76.1

[06kellyjac]

Things done

• go-mockery: 2.52.1 -> 2.53.2
  • required to fix terragrunt: failed to upgrade #389694
  • also adopts latest go to work with projects using latest go
    • replaces go-mockery: 2.52.1 -> 2.52.4 #386264
    • cross-ref go: write down toolchain/builder upgrade policy; introduce go_latest/buildGoLatestModule #384229
  • runs go tests
  • didn't add versionCheckHook since I couldn't get it to work and it's covered by passthru test
  • use meta.mainProgram in passthru test
  • join as a maintainer - cc: @cideM
• terragrunt: 0.75.10 -> 0.76.1
  • update
  • replace manual version check with versionCheckHook

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[atkrad]

Hello, Is there any update?

[cideM]

I don't feel like it's my call to stand in the way of fixing a package. I only have what is ultimately a minor question about the usage of go_1_24, which can be resolved after merging this.

[r-vdp]

It seems that unstable is already at 1.24, isn't it? So what's the purpose of the version pin here? I would prefer to unpin and then just merge. Any objections?

[06kellyjac]

The objections to unpinning have already been raised.

I'll rehash the reasoning again, pulling from an existing PR with it pinned, identifying the package as being version sensitive, being exactly the same.

#390700 has been merged and now this PR needs rebasing

IMO we should be able to get build fixing PRs into unstable in less than 4 days, let alone master

[Mic92]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 389836

---

aarch64-darwin

✅ 3 packages built:

• git-team
• go-mockery
• terragrunt