hpack: 0.36.1 -> 0.37.0

[9999years]

The latest version of Haskell's hpack is 0.37.0. Increasingly .cabal files begin with a comment that causes Nixpkgs' hpack to reject them entirely:

-- This file has been generated from package.yaml by hpack version 0.37.0.
--
-- see: https://github.com/sol/hpack

$ hpack
shellwords.cabal was generated with a newer version of hpack, please upgrade and try again.

Unfortunately, hpack's --force option does not override this error; you need to remove the .cabal file in question manually, which can be annoying in repositories with many package.yaml files.

Using the latest version of hpack, which is provided by Nixpkgs but not set as the default for unclear reasons. hpack ==0.36.1 is listed as a constraint in
pkgs/development/configuration-hackage2nix/stackage.yaml, but pkgs/development/haskell-modules/configuration-common.nix makes sure to set hpack = self.hpack_0_37_0 for Stack itself.

See: pkgs/test/haskell/upstreamStackHpackVersion/default.nix

Things done

• 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.

[9999years]

I've added a warning here in case hpack gets updated past 0.37.0 without us noticing.

[9999years]

@sternenseemann Do you know why hpack is pinned to 0.36.1? I'm not super clear on the hackage2nix machinery so there might be some context I'm missing.

[sternenseemann]

We inherit the hpack version from Stackage which restricts hpack to a specific version range that doesn't cause brakage according to PVP. hpack's library only has few reverse dependencies so we can probably use the latest version by default to begin with, e.g.:

nixpkgs/maintainers/scripts/haskell/update-stackage.sh

Lines 58 to 74 in 3566ab7

	# Drop restrictions on some tools where we always want the latest version.
	sed -r \
	-e '/ cabal2nix /d' \
	-e '/ distribution-nixpkgs /d' \
	-e '/ jailbreak-cabal /d' \
	-e '/ language-nix /d' \
	-e '/ hackage-db /d' \
	-e '/ cabal-install /d' \
	-e '/ cabal-install-solver /d' \
	-e '/ lsp /d' \
	-e '/ lsp-types /d' \
	-e '/ lsp-test /d' \
	-e '/ hie-bios /d' \
	-e '/ ShellCheck /d' \
	-e '/ Agda /d' \
	-e '/ stack /d' \
	< "${tmpfile_new}" >> $stackage_config

[9999years]

@sternenseemann Thanks! It looks like hpack has been upgraded to 0.37 in the latest Stackage LTS ("LTS 23.0 for ghc-9.8.4, published 4 days ago"). Should I run maintainers/scripts/haskell/update-stackage.sh and open a PR to haskell-updates?