From c841fd15cdb9d3e6dcd7ab56df34753c73664cd3 Mon Sep 17 00:00:00 2001 From: anthony Date: Sat, 27 Apr 2024 08:48:25 -0400 Subject: [PATCH] update ref `@v6` to `@v7` --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8034201..1e9b448 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,8 @@ The `hashicorp/setup-terraform` action is a JavaScript action that sets up Terra - Downloading a specific version of Terraform CLI and adding it to the `PATH`. - Configuring the [Terraform CLI configuration file](https://www.terraform.io/docs/commands/cli-config.html) with a Terraform Cloud/Enterprise hostname and API token. -- Installing a wrapper script to wrap subsequent calls of the `terraform` binary and expose its STDOUT, STDERR, and exit code as outputs named `stdout`, `stderr`, and `exitcode` respectively. (This can be optionally skipped if subsequent steps in the same job do not need to access the results of Terraform commands.) +- Installing a wrapper script to wrap subsequent calls of the `terimage +raform` binary and expose its STDOUT, STDERR, and exit code as outputs named `stdout`, `stderr`, and `exitcode` respectively. (This can be optionally skipped if subsequent steps in the same job do not need to access the results of Terraform commands.) After you've used the action, subsequent steps in the same job can run arbitrary Terraform commands using [the GitHub Actions `run` syntax](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun). This allows most Terraform commands to work exactly like they do on your local command line. @@ -179,7 +180,7 @@ steps: run: terraform plan -no-color continue-on-error: true -- uses: actions/github-script@v6 +- uses: actions/github-script@v7 if: github.event_name == 'pull_request' env: PLAN: "terraform\n${{ steps.plan.outputs.stdout }}"