CI broken on main

[KiaraGrouwstra]

Describe the bug
CI currently fails including on main, even though its commits ran successfully when merged, implying the old situation is not reproducible, possibly due to CI using nixos-stable.

To Reproduce

1. git checkout main
2. nix run .#test-examples
3. find error:

+ nix develop --accept-flake-config --override-input tf-ncl /nix/store/w2d1qzzd7d35xzn64nm8d6r18y1fmkar-source -c run-nickel
warning: not writing modified lock file of flake 'path:/tmp/tmp.vV5CrBNFWw':
• Updated input 'tf-ncl':
    'github:tweag/tf-ncl/2f3c91c761669cfb76d3c2401a00d1eca71ceb12' (2023-09-05)
  → 'path:/nix/store/w2d1qzzd7d35xzn64nm8d6r18y1fmkar-source?lastModified=0&narHash=sha256-Rny%2BjWKck9ConQpvgXGh%2BnJ6P2%2BJS%2B0BJBLxoDNxOTw%3D' (1970-01-01)
• Updated input 'tf-ncl/nixpkgs':
    'github:NixOS/nixpkgs/b12803b6d90e2e583429bb79b859ca53c348b39a' (2023-07-24)
  → 'github:nixos/nixpkgs/bffc22eb12172e6db3c5dde9e3e5628f8e3e7912' (2025-01-08)
error:
       … while evaluating 'strict' to select 'drvPath' on it
         at /builtin/derivation.nix:1:552:
       … while calling the 'derivationStrict' builtin
         at /builtin/derivation.nix:1:208:
       (stack trace truncated; use '--show-trace' to show the full trace)

       error: attribute 'overrideScope'' missing
       at /nix/store/q6y6d512iwxs8qplsgsn14jkbwdawg96-source/lib/default.nix:54:34:
           53|
           54|   overrideToolchain = toolchain: self.overrideScope' (_final: _prev: {
             |                                  ^
           55|     cargo = toolchain;
       Did you mean overrideScope?

Expected behavior
no error

Environment

• NixOS 24.11
• Version of the code: main

Additional context
this came up at #69 (review)

[yannham]

I can reproduce the same error on #72. Thanks for reporting, will dig.

[yannham]

Given nix-community/lanzaboote#411, it seems that one of the crane is still blocked at a version that used overrideScope'. We pull 3 different crane versions (from Nickel, from Topiary, and for tf-ncl); I'm trying to play with .follows to see if I can get the offending version not be here anymore.