ci gitlab clear global index state #9344
Conversation
andreabedini
force-pushed
the
andrea/ci-gitlab-clear-global-index-state
branch
from
b5acff6
to
f1fe412
Compare
|
I think it would be fine to move to Cabal 3.8+ to build the release. It's not the release pipeline's job to test backward compatibility, right? Then we don't have to have the message about working around a bug in 3.6. |
andreabedini
force-pushed
the
andrea/ci-gitlab-clear-global-index-state
branch
from
f1fe412
to
6fe5441
Compare
andreabedini
force-pushed
the
andrea/ci-gitlab-clear-global-index-state
branch
from
6fe5441
to
15f53b8
Compare
There was a problem hiding this comment.
I think it would be fine to move to Cabal 3.8+ to build the release. It's not the release pipeline's job to test backward compatibility, right? Then we don't have to have the message about working around a bug in 3.6.
@andreabedini on second thought, now is absolutely the wrong time to do that, cause it might break other things, so disregard the suggestion.
I guess this is probably good enough for now!
You've cherry picked my other fix, though, and meanwhile I'm also trying to make an i386-alpine release job. So rather than merge them individually, maybe let's make one single change. Let me finish the 3rd patch and then we can combine them.
|
Closing in favor of #9348 |
cabal updatealone will update the tarball but preserve the global index state if one is set.