Skip to content

Relax http-client-tls upper bound to allow 0.4 #14

Relax http-client-tls upper bound to allow 0.4

Relax http-client-tls upper bound to allow 0.4 #14

Triggered via pull request June 25, 2026 15:18
Status Failure
Total duration 10s
Artifacts

ci.yml

on: pull_request
Matrix: cabal
Matrix: stack
Fit to window
Zoom out
Zoom in

Annotations

20 errors
cabal / ghc-9.0.2 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
cabal / ghc-9.6.6 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
cabal / ghc-8.10.7 / ubuntu-latest
The strategy configuration was canceled because "cabal.ubuntu-latest_latest_9_2_" failed
cabal / ghc-9.2.8 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
cabal / ghc-8.10.7 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
cabal / ghc-9.4.8 / ubuntu-latest
The strategy configuration was canceled because "cabal.ubuntu-latest_latest_9_2_" failed
cabal / ghc-9.4.8 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
stack --stack-yaml ./stack-9.0.yaml / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
stack --stack-yaml ./stack-9.4.yaml / ubuntu-latest
The strategy configuration was canceled because "stack.ubuntu-latest_latest_--_2" failed
stack --stack-yaml ./stack-9.4.yaml / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
stack --stack-yaml ./stack-8.10.yaml / ubuntu-latest
The strategy configuration was canceled because "stack.ubuntu-latest_latest_--_2" failed
stack --stack-yaml ./stack-8.10.yaml / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
stack --stack-yaml ./stack-9.6.yaml / ubuntu-latest
The strategy configuration was canceled because "stack.ubuntu-latest_latest_--_2" failed
stack --stack-yaml ./stack-9.6.yaml / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
cabal / ghc-9.8.2 / ubuntu-latest
The strategy configuration was canceled because "cabal.ubuntu-latest_latest_9_2_" failed
cabal / ghc-9.8.2 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
cabal / ghc-9.10.1 / ubuntu-latest
The strategy configuration was canceled because "cabal.ubuntu-latest_latest_9_2_" failed
cabal / ghc-9.10.1 / ubuntu-latest
The actions actions/checkout@v4, haskell-actions/setup@v2, and actions/cache@v3 are not allowed in bitnomial/prometheus because all actions must be pinned to a full-length commit SHA.
stack --stack-yaml ./stack-9.2.yaml / ubuntu-latest
The strategy configuration was canceled because "stack.ubuntu-latest_latest_--_2" failed
stack --stack-yaml ./stack-9.2.yaml / ubuntu-latest
The operation was canceled.