Tried to record deployment manually on my local machine, and it worked fine. But fails in ci/cd

I reproduced the error and this behaviour looks weird to me. For example, I have the following ci/cd set up in GitLab where I specify

PROVIDER_VERSION

in variables and then I pass this variable to the record deployment job:

verify contracts:
  stage: validate
  extends: .pact-aws-cli-v1
  variables:
    PROVIDER_VERSION: $CI_COMMIT_SHA
  script:
    - >-
      pact-verifier
      --hostname="app"
      --broker-url="$PACT_FLOW_BASE_URL"
      --token="$PACT_FLOW_KEY"
      --loglevel="info"
      --provider-branch="$CI_COMMIT_REF_SLUG"
      --provider-version="$PROVIDER_VERSION"
      --provider-tags="$CI_COMMIT_REF_NAME"
      --consumer-version-tags="main"
      --provider-name=dummy-microservice-provider
      --publish



record deployment in pact:
  stage: record deployment
  extends: .pact-aws-cli-v1
  variables:
    ENVIRONMENT: $ENVIRONMENT
  script:
    - >-
      pact-broker record-deployment
      --pacticipant=dummy-microservice-provider
      --version="$PROVIDER_VERSION"
      --environment="$ENVIRONMENT"
      --broker-base-url="$PACT_FLOW_BASE_URL"
      --broker-token="$PACT_FLOW_KEY"
      --verbose

and in this case record deployment fails with the error above. If I provide

--version=$CI_COMMIT_SHA

in the

record deployment

job everything works. Why I can’t use

PROVIDER_VERSION

defined in variables? And an interesting thing, it works for

can-i-deploy

well, specifying PROVIDER_VERSION in global variables helped:

variables:
  PROVIDER_VERSION: $CI_COMMIT_SHA