chore(deps): update codefresh/cli docker tag to v0.88.4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
codefresh/cli	final	minor	0.74.9 -> 0.88.4

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[bridgecrew]

Bridgecrew has found errors in this PR ⬇️

[bridgecrew]

  Ensure a user for the container has been created
    Resource: /codefresh/pipeline-runner/Dockerfile. | Bridgecrew ID: BC_DKR_3 | Checkov ID: CKV_DOCKER_3

Description

Containers should run as a non-root user. It is good practice to run the container as a non-root user, where possible. This can be done either via the ```USER``` directive in the ```Dockerfile``` or through ```gosu``` or similar where used as part of the ```CMD``` or ```ENTRYPOINT``` directives.

Benchmarks

• CIS DOCKER V1.2 4.1

     🎉   Fixed by commit 88fca04 - chore(deps): update codefresh/cli docker tag to v0.87.1

[bridgecrew]

  Ensure healthcheck instructions have been added to container images
    Resource: /codefresh/pipeline-creator/Dockerfile. | Bridgecrew ID: BC_DKR_2 | Checkov ID: CKV_DOCKER_2

Description

We recommend that you add the HEALTHCHECK instruction to your Docker container images to ensure that health checks are executed against running containers.

An important security control is that of availability. Adding the HEALTHCHECK instruction to your container image ensures that the Docker engine periodically checks the running container instances against that instruction to ensure that containers are still operational.

Based on the results of the health check, the Docker engine could terminate containers which are not responding correctly, and instantiate new ones.

Benchmarks

• CIS DOCKER V1.2 4.6

     🎉   Fixed by commit 88fca04 - chore(deps): update codefresh/cli docker tag to v0.87.1

[bridgecrew]

  Ensure healthcheck instructions have been added to container images
    Resource: /codefresh/pipeline-runner/Dockerfile. | Bridgecrew ID: BC_DKR_2 | Checkov ID: CKV_DOCKER_2

Description

We recommend that you add the HEALTHCHECK instruction to your Docker container images to ensure that health checks are executed against running containers.

An important security control is that of availability. Adding the HEALTHCHECK instruction to your container image ensures that the Docker engine periodically checks the running container instances against that instruction to ensure that containers are still operational.

Based on the results of the health check, the Docker engine could terminate containers which are not responding correctly, and instantiate new ones.

Benchmarks

• CIS DOCKER V1.2 4.6

     🎉   Fixed by commit 88fca04 - chore(deps): update codefresh/cli docker tag to v0.87.1

[bridgecrew]

  Ensure a user for the container has been created
    Resource: /codefresh/pipeline-creator/Dockerfile. | Bridgecrew ID: BC_DKR_3 | Checkov ID: CKV_DOCKER_3

Description

Containers should run as a non-root user. It is good practice to run the container as a non-root user, where possible. This can be done either via the ```USER``` directive in the ```Dockerfile``` or through ```gosu``` or similar where used as part of the ```CMD``` or ```ENTRYPOINT``` directives.

Benchmarks

• CIS DOCKER V1.2 4.1

     🎉   Fixed by commit 88fca04 - chore(deps): update codefresh/cli docker tag to v0.87.1