Cherry-pick of 41ce532 has failed:

On branch mergify/bp/3.14/pr-10664
Your branch is up to date with 'origin/3.14'.

You are currently cherry-picking commit 41ce532cf.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   cabal.release.project

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Git rev stuff un-cherry-picked; that can be backported later if desired.

[__1] rejecting: unix-2.8.4.0/installed-2.8.4.0 (conflict: Cabal => unix>=2.8.6.0 && <2.9)

https://github.com/haskell/cabal/actions/runs/12527156226/job/34940451295?pr=10665#step:6:12

Why has index-state in this patch been downgraded from November to September 2024?

Probably my fault when I resolved a conflict.

That solved the solver issue.

Yeh, you have to be careful about that when resolving conflicts, I saw it multiple times while backporting fixes.

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

@Mergifyio requeue

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

@Kleidukos I think this PR isn't needed after b28ee38 (already on 3.14 branch).

It needed rebase, which I did. But I took off the merge labels, so that @Kleidukos can decide whether we do it or not. I think we don't need it...

Perfect, if the constraints are already fixed that doesn't bother me to abort this PR.