stable:latest still has terraform 0.13.4 instead 0.13.5 after bump

Hello,

about a week ago !32 (merged) was merged updating Terraform base from 0.13.4 to 0.13.5. I checked locally with running docker run -it registry.gitlab.com/gitlab-org/terraform-images/stable:latest gitlab-terraform version. Output was

+ plan_cache=plan.cache
+ plan_json=plan.json
+ JQ_PLAN='
  (
    [.resource_changes[]?.change.actions?] | flatten
  ) | {
    "create":(map(select(.=="create")) | length),
    "update":(map(select(.=="update")) | length),
    "delete":(map(select(.=="delete")) | length)
  }
'
+ TF_USERNAME=
+ '[' -z  ]
+ TF_USERNAME=gitlab-ci-token
+ TF_PASSWORD=
+ '[' -n  ]
+ export 'TF_HTTP_ADDRESS='
+ export 'TF_HTTP_LOCK_ADDRESS=/lock'
+ export 'TF_HTTP_LOCK_METHOD=POST'
+ export 'TF_HTTP_UNLOCK_ADDRESS=/lock'
+ export 'TF_HTTP_UNLOCK_METHOD=DELETE'
+ export 'TF_HTTP_USERNAME=gitlab-ci-token'
+ export 'TF_HTTP_PASSWORD='
+ export 'TF_HTTP_RETRY_WAIT_MIN=5'
+ terraform version
Terraform v0.13.4

Your version of Terraform is out of date! The latest version
is 0.13.5. You can update by downloading from https://www.terraform.io/downloads.html

I expected this to be Terraform v0.13.5.

I checked the release process and on tags, new release should be made, including tagging stable:latest to latest version. After checking pipelines, no release was made on tag v0.3.2. I would consider it a bug. There was a change to .gitlab-ci.yml which had two previously failed pipelines because of invalid yaml, maybe this change (46b52b4d) broke this.

Have a look at the spoken pipeline (tag vO.3.2) https://gitlab.com/gitlab-org/terraform-images/-/pipelines/208897038 Here is pipeline for a previous tag v0.3.1 https://gitlab.com/gitlab-org/terraform-images/-/pipelines/196942915

My CI is failing, since locally I am using Terraform v0.13.5, but in CI v0.13.4 is used. Where Terraform panics on this with following error: Error refreshing state: state snapshot was created by Terraform v0.13.5, which is newer than current v0.13.4; upgrade to Terraform v0.13.5 or greater to work with this state

Thank you for investigating this. Maybe I am not familiar enough with the release process of GitLab's Terraform images and I am missing something, but from looking on previous tag's pipeline, this should have ran.