gitlab: 16.10.6 -> 16.11.4

[yayayayaka]

• https://about.gitlab.com/releases/2024/06/12/patch-release-gitlab-17-0-2-released/
• Fixes CVE-2024-1495
• Fixes CVE-2024-1963
• Fixes CVE-2024-4201
• Fixes CVE-2024-5469

Description of changes

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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

[vcunat]

I'm confused about this test
@ofborg build nixosTests.gitlab

As what I see is failure since the last staging-next (PR #316075), with lots of "Early termination of worker" and the test timing out (locally and on Hydra). This PR doesn't help that issue, according to my testing, but the CI here looked like success :-/ This test failure blocks nixos-unstable now, BTW.

[vcunat]

Both *-linux passed the test in ofBorg. So that is weird.

[yayayayaka]

Even after rebasing to the latest master commit, the NixOS test is still building fine for me locally.

[vcunat]

It passed for me now. So I'm not sure if I made a mistake when trying this PR atop nixpkgs master? (and it's actually fixing the test) Or is it flaky?

[vcunat]

I think this PR solves the test failure.

[K900]

Let's just merge this, it's a security fix and blocks the channel.

[github-actions]

Backport failed for release-23.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-23.11
git worktree add -d .worktree/backport-319486-to-release-23.11 origin/release-23.11
cd .worktree/backport-319486-to-release-23.11
git switch --create backport-319486-to-release-23.11
git cherry-pick -x 7e9c87c67b97efa5c174fde31426a5df2369ab72 e34d62d869c3fbd23ab7440628bfea28b1e176c2

[github-actions]

Successfully created backport PR for release-24.05:

• [Backport release-24.05] gitlab: 16.10.6 -> 16.11.4 #319559