fix network-uri bound

[geekosaur]

Someone (I won't claim it wasn't me) swapped digits in the dependency for cabal-install. But it's correct for the later tests, which makes me think it was a typo.

---

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

[ulysses4ever]

git-blame tells me that the current bound was committed in 2018 4aea51a, which is 1+ year before network-uri-2.6.2.0 was released (https://hackage.haskell.org/package/network-uri-2.6.2.0). So, I doubt 2.6.0.2 is a typo.

[ulysses4ever]

In the light of the corresponding issue, this looks necessary.

I wish we had a --prefer-oldest CI configuration...

[geekosaur]

I'm still poking at using special comments to trigger customized CI runs; if I can figure it out (currently it looks like I'll need or at least really want a separate job triggered only on comments, since otherwise there'll have to be magic conditionals all over the place) I could probably add one. Can't be too general, though, since it has to be written to the project file instead of passed as an option.

[geekosaur]

Blame won't really tell you anything here, since git goes by diffs and someone accidentally re-typing the same bound won't show up as a change.

[mniip]

I think network-uri-2.6.0.2 was chosen as a lower bound because that's where instance NFData URI was introduced, which cabal-install uses

[geekosaur]

@mergify backport 3.16

[mergify]

backport 3.16

✅ Backports have been created

• #11241 Backport #11230: fix network-uri bound has been created for branch 3.16