prisma-engines: 4.11.0 -> 4.12.0

[ivan]

Description of changes

prisma/prisma-engines@4.11.0...4.12.0

https://github.com/prisma/prisma/releases/tag/4.12.0

I removed "-p" "introspection-core" because introspection-core is gone in prisma-engines.

I copied Cargo.lock from [email protected].

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 23.05 Release Notes (or backporting 22.11 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.

cc maintainers @Pamplemousse @pimeys @tomhoule

[tomhoule]

It doesn't relate directly to this PR, but I don't understand why we have a committed Cargo.lock in nixpkgs now, it wasn't the case until very recently and I didn't get a notification when that happened. Git blame points to 0f2c778 but that's not super helpful. Does anybody have more context?

Otherwise the PR looks good to me. You might want to update nodePackages.prisma too.

[tomhoule]

Ok found when and how that happened: #221716

[lucasew]

Result of nixpkgs-review pr 223700 run on x86_64-linux 1

1 package built:

• prisma-engines

[pimeys]

Hey, @ivan! Thanks for this, we need more maintainers.

One thing missing is that by just updating prisma-engines, you are breaking nodePackages.prisma. You can try out building it, which will give you an error of a wrong sha sum.

Just update the new sum, rebuild and create two commits: one updating prisma-engines and another nodePackages.prisma.

[ivan]

@pimeys thanks for the review. I updated the hash for nodePackages.prisma now.

[lucasew]

Result of nixpkgs-review pr 223700 run on x86_64-linux 1

1 package built:

• prisma-engines