Resolve markdownlint warnings for CHANGELOG.md

Author: dflook

CHANGELOG.md

@@ -31,9 +31,9 @@ When using an action you can specify the version as:
 
 ### Added
 - Support for Terraform 1.10 ephemeral input variables.
-    
+
   Terraform 1.10 introduced ephemeral values, which are not stored in the plan or state file.
-  Ephemeral variables now work correctly with [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/main/terraform-apply). 
+  Ephemeral variables now work correctly with [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/main/terraform-apply).
   These can be set normally using the `variables` input.
 
 ## [1.45.0] - 2024-12-24
@@ -70,7 +70,7 @@ When using an action you can specify the version as:
   This is only useful to avoid rate limiting when using the actions with GitHub Enterprise together with OpenTofu.
 
   Normally the `GITHUB_TOKEN` environment variable is used for API requests. When using GitHub Enterprise, the `GITHUB_TOKEN` is the token for the GitHub Enterprise instance, and not the GitHub.com API.
-  OpenTofu requires the GitHub.com API to fetch release information. 
+  OpenTofu requires the GitHub.com API to fetch release information.
 
 ## [1.41.2] - 2024-02-11
 
@@ -95,7 +95,7 @@ When using an action you can specify the version as:
 - An optional `plan_path` input for [dflook/terraform-apply](terraform-apply), and matching `plan_path` output for [dflook/terraform-plan](terraform-plan).
 
   This allows passing the generated plan from the plan step to the apply step, if you have a secure place to store it.
- 
+
   The default behaviour when this is not set is unchanged - the apply step will generate a fresh plan and compare it to the plan from the PR comment.
   By passing the plan from the plan step to the apply step, the apply step will skip generating a plan and use the passed plan instead.
   It must still match the plan in the PR comment.
@@ -140,29 +140,29 @@ When using an action you can specify the version as:
   When [dflook/terraform-apply](terraform-apply) applies a plan, any PR comment will be updated with the results of the apply, and then no further updates will be made.
   Any further plans generated by [dflook/terraform-plan](terraform-plan) will result in a new plan in a different PR comment.
 
-  This is to avoid the comment being updated after the plan has been applied, which can be confusing. 
+  This is to avoid the comment being updated after the plan has been applied, which can be confusing.
   This would only happen if your workflow is to apply changes before merging the PR.
 
 ## [1.37.0] - 2023-10-29
 
 ### Added
 
-- Experimental support for OpenTofu. 
+- Experimental support for OpenTofu.
 
   New tofu actions have been added that are identical to the terraform actions, but use OpenTofu instead of Terraform for versions >= 1.6.0.:
-  - [dflook/tofu-version](tofu-version)
-  - [dflook/tofu-remote-state](tofu-remote-state)
-  - [dflook/tofu-output](tofu-output)
-  - [dflook/tofu-validate](tofu-validate)
-  - [dflook/tofu-fmt-check](tofu-fmt-check)
-  - [dflook/tofu-fmt](tofu-fmt)
-  - [dflook/tofu-check](tofu-check)
-  - [dflook/tofu-plan](tofu-plan)
-  - [dflook/tofu-apply](tofu-apply)
-  - [dflook/tofu-destroy](tofu-destroy)
-  - [dflook/tofu-new-workspace](tofu-new-workspace)
-  - [dflook/tofu-destroy-workspace](tofu-destroy-workspace)
-  - [dflook/tofu-unlock-state](tofu-unlock-state)
+  * [dflook/tofu-version](tofu-version)
+  * [dflook/tofu-remote-state](tofu-remote-state)
+  * [dflook/tofu-output](tofu-output)
+  * [dflook/tofu-validate](tofu-validate)
+  * [dflook/tofu-fmt-check](tofu-fmt-check)
+  * [dflook/tofu-fmt](tofu-fmt)
+  * [dflook/tofu-check](tofu-check)
+  * [dflook/tofu-plan](tofu-plan)
+  * [dflook/tofu-apply](tofu-apply)
+  * [dflook/tofu-destroy](tofu-destroy)
+  * [dflook/tofu-new-workspace](tofu-new-workspace)
+  * [dflook/tofu-destroy-workspace](tofu-destroy-workspace)
+  * [dflook/tofu-unlock-state](tofu-unlock-state)
 
   As OpenTofu currently only has pre-release versions, OpenTofu will only be selected by using the exact version number.
   The easiest way to do this is by setting the `OPENTOFU_VERSION` environment variable, e.g in your workflow:
@@ -205,7 +205,7 @@ When using an action you can specify the version as:
 ## [1.35.0] - 2023-06-18
 
 ### Added
-- Support for partial or empty cloud blocks. This means you can use a placeholder `cloud` block in your terraform, like so: 
+- Support for partial or empty cloud blocks. This means you can use a placeholder `cloud` block in your terraform, like so:
 
 ```hcl
 terraform {
@@ -249,7 +249,7 @@ terraform {
 
 ### Changed
 - If a terraform operation fails because the state is locked the `failure-reason` output will now be set to `state-locked`,
-  where before it may have been `apply-failed` or `destroy-failed`. 
+  where before it may have been `apply-failed` or `destroy-failed`.
 
 ## [1.31.1] - 2022-12-01
 
@@ -273,7 +273,7 @@ terraform {
 ## [1.29.1] - 2022-10-24
 
 ### Fixed
-- Multiline string terraform outputs are now properly set as action outputs, and properly masked in the workflow log. 
+- Multiline string terraform outputs are now properly set as action outputs, and properly masked in the workflow log.
 
 ## [1.29.0] - 2022-10-17
 
@@ -321,15 +321,16 @@ terraform {
 ## [1.25.0] - 2022-05-06
 
 ### Added
-- New `run_id` output for [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/main/terraform-plan) and [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/main/terraform-apply) which are set when using Terraform Cloud/Enterprise. It is the remote run-id of the plan or apply operation.
+- New `run_id` output for [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/main/terraform-plan) and [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/main/terraform-apply) which are set when using Terraform Cloud/Enterprise.
+  It is the remote run-id of the plan or apply operation.
 - The `json_plan_path` output of [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/main/terraform-plan) now works when using Terraform Cloud/Enterprise.
 
 ## [1.24.0] - 2022-05-03
 
 ### Added
 - New `to_add`, `to_change` and `to_destroy` outputs for the [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/main/terraform-plan) action that contain the number of resources that would be added, changed or deleted by the plan.
 
-  These can be used in an [if expression](https://docs.github.com/en/enterprise-server@3.2/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif) in a workflow to conditionally run steps, e.g. when the plan would destroy something. 
+  These can be used in an [if expression](https://docs.github.com/en/enterprise-server@3.2/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idif) in a workflow to conditionally run steps, e.g. when the plan would destroy something.
 
 ## [1.23.0] - 2022-05-02
 
@@ -343,7 +344,7 @@ terraform {
 ### Fixed
 - Pre-release terraform versions now won't be used when selecting the latest terraform version.
 - Invalid terraform files that contained an unterminated string would take an extremely long time to parse before failing the job.
-- [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate) now automatically sets `terraform.workspace` to `default` when validating a module that uses a `remote` or `cloud` backend. 
+- [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate) now automatically sets `terraform.workspace` to `default` when validating a module that uses a `remote` or `cloud` backend.
 
 ## [1.22.2] - 2022-02-28
 
@@ -360,16 +361,17 @@ terraform {
 
 ### Added
 - Workspace management for Terraform Cloud/Enterprise has been reimplemented to avoid issues with the `terraform workspace` command when using the `remote` backend or a cloud config block:
-  - [dflook/terraform-new-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-new-workspace) can now create the first workspace
-  - [dflook/terraform-destroy-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-destroy-workspace) can now delete the last remaining workspace
-  - [dflook/terraform-new-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-new-workspace) and [dflook/terraform-destroy-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-destroy-workspace) work with a `remote` backend that specifies a workspace by `name`
+  * [dflook/terraform-new-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-new-workspace) can now create the first workspace
+  * [dflook/terraform-destroy-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-destroy-workspace) can now delete the last remaining workspace
+  * [dflook/terraform-new-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-new-workspace) and [dflook/terraform-destroy-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-destroy-workspace)
+    work with a `remote` backend that specifies a workspace by `name`
 
 - The terraform version to use will now be detected from additional places:
 
-  - The terraform version set in the remote workspace when using Terraform Cloud/Enterprise as the backend 
-  - An [asdf](https://asdf-vm.com/) `.tool-versions` file
-  - The terraform version that wrote an existing state file
-  - A `TERRAFORM_VERSION` environment variable
+  * The terraform version set in the remote workspace when using Terraform Cloud/Enterprise as the backend
+  * An [asdf](https://asdf-vm.com/) `.tool-versions` file
+  * The terraform version that wrote an existing state file
+  * A `TERRAFORM_VERSION` environment variable
 
   The best way to specify the version is using a [`required_version`](https://www.terraform.io/docs/configuration/terraform.html#specifying-a-required-terraform-version) constraint.
 
@@ -378,13 +380,19 @@ terraform {
 ### Changed
 As a result of the above terraform version detection additions, note these changes:
 
-- Actions always use the terraform version set in the remote workspace when using TFC/E, if it exists. This mostly effects [dflook/terraform-fmt](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt), [dflook/terraform-fmt-check](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt-check) and [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate).
+- Actions always use the terraform version set in the remote workspace when using TFC/E, if it exists. This mostly
+  effects [dflook/terraform-fmt](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt),
+  [dflook/terraform-fmt-check](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt-check) and
+  [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate).
 
 - If the terraform version is not specified anywhere then new workspaces will be created with the latest terraform version. Existing workspaces will use the terraform version that was last used for that workspace.
 
 - If you want to always use the latest terraform version, instead of not specifying a version you now need to set an open-ended version constraint (e.g. `>1.0.0`)
 
-- All actions now support the inputs and environment variables related to the backend, for discovering the terraform version from a TFC/E workspace or remote state. This add the inputs `workspace`, `backend_config`, `backend_config_file`, and the `TERRAFORM_CLOUD_TOKENS` environment variable to the [dflook/terraform-fmt](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt), [dflook/terraform-fmt-check](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt-check) and [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate) actions.
+- All actions now support the inputs and environment variables related to the backend, for discovering the terraform
+  version from a TFC/E workspace or remote state. This add the inputs `workspace`, `backend_config`,
+  `backend_config_file`, and the `TERRAFORM_CLOUD_TOKENS` environment variable to the [dflook/terraform-fmt](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt),
+  [dflook/terraform-fmt-check](https://github.com/dflook/terraform-github-actions/tree/main/terraform-fmt-check) and [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate) actions.
 
 - :warning: Some unused packages were removed from the container image, most notably Python 2.
 
@@ -394,14 +402,14 @@ As a result of the above terraform version detection additions, note these chang
 - [dflook/terraform-new-workspace](https://github.com/dflook/terraform-github-actions/tree/main/terraform-new-workspace) support for Terraform v1.1.0.
 
   This stopped working after a change in the behaviour of terraform init.
- 
+
   There is an outstanding [issue in Terraform v1.1.0](https://github.com/hashicorp/terraform/issues/30129) using the `remote` backend that prevents creating a new workspace when no workspaces currently exist.
   If you are affected by this, you can pin to an earlier version of Terraform using one of methods listed in the [dflook/terraform-version](https://github.com/dflook/terraform-github-actions/tree/main/terraform-version#terraform-version-action) docs.
 
 ## [1.21.0] - 2021-12-04
 
 ### Added
-- A new `workspace` input for [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate) 
+- A new `workspace` input for [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/main/terraform-validate)
   allows validating usage of `terraform.workspace` in the terraform code.
 
   Terraform doesn't initialize `terraform.workspace` based on the backend configuration when running a validate operation.
@@ -420,7 +428,8 @@ As a result of the above terraform version detection additions, note these chang
 
   These are paths to the generated plan in human-readable and JSON formats.
 
-  If the plan generated by [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/main/terraform-plan) is different from the plan generated by [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/main/terraform-apply) the apply step will fail with `failure-reason` set to `plan-changed`.
+  If the plan generated by [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/main/terraform-plan) is different from the plan generated by
+  [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/main/terraform-apply) the apply step will fail with `failure-reason` set to `plan-changed`.
   These new outputs make it easier to inspect the differences.
 
 ## [1.19.0] - 2021-11-01
@@ -454,6 +463,13 @@ As a result of the above terraform version detection additions, note these chang
       kubernetes_secret.tls_cert_private
   ```
 
+## [1.17.3] - 2021-10-29
+
+### Fixed
+- [dflook/terraform-new-workspace](https://github.com/dflook/terraform-github-actions/tree/master/terraform-new-workspace)
+  compatability with Terraform v1.0.10 - Thanks [kylewlacy](https://github.com/kylewlacy)!
+- Now makes even fewer GitHub api requests to avoid rate limiting.
+
 ## [1.17.2] - 2021-10-13
 
 ### Fixed
@@ -479,8 +495,8 @@ As a result of the above terraform version detection additions, note these chang
 
 ### Added
 - [dflook/terraform-plan](https://github.com/dflook/terraform-github-actions/tree/master/terraform-plan) has gained two new outputs:
-  - `json_plan_path` is a path to the generated plan in a JSON format file
-  - `text_plan_path` is a path to the generated plan in a human-readable text file
+  * `json_plan_path` is a path to the generated plan in a JSON format file
+  * `text_plan_path` is a path to the generated plan in a human-readable text file
 
   These paths are relative to the GitHub Actions workspace and can be read by other steps in the same job.
 
@@ -490,12 +506,12 @@ As a result of the above terraform version detection additions, note these chang
 - Actions that intentionally cause a build failure now set a `failure-reason` output to enable safely responding to those failures.
 
   Possible failure reasons are:
-  - [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/master/terraform-validate#outputs): validate-failed
-  - [dflook/terraform-fmt-check](https://github.com/dflook/terraform-github-actions/tree/master/terraform-fmt-check#outputs): check-failed
-  - [dflook/terraform-check](https://github.com/dflook/terraform-github-actions/tree/master/terraform-check#outputs): changes-to-apply
-  - [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/master/terraform-apply#outputs): apply-failed, plan-changed
-  - [dflook/terraform-destroy](https://github.com/dflook/terraform-github-actions/tree/master/terraform-destroy#outputs): destroy-failed
-  - [dflook/terraform-destroy-workspace](https://github.com/dflook/terraform-github-actions/tree/master/terraform-destroy-workspace#outputs): destroy-failed
+  * [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/master/terraform-validate#outputs): validate-failed
+  * [dflook/terraform-fmt-check](https://github.com/dflook/terraform-github-actions/tree/master/terraform-fmt-check#outputs): check-failed
+  * [dflook/terraform-check](https://github.com/dflook/terraform-github-actions/tree/master/terraform-check#outputs): changes-to-apply
+  * [dflook/terraform-apply](https://github.com/dflook/terraform-github-actions/tree/master/terraform-apply#outputs): apply-failed, plan-changed
+  * [dflook/terraform-destroy](https://github.com/dflook/terraform-github-actions/tree/master/terraform-destroy#outputs): destroy-failed
+  * [dflook/terraform-destroy-workspace](https://github.com/dflook/terraform-github-actions/tree/master/terraform-destroy-workspace#outputs): destroy-failed
 
 ### Fixed
 - [dflook/terraform-validate](https://github.com/dflook/terraform-github-actions/tree/master/terraform-validate) was sometimes unable to create detailed check failures.
@@ -525,6 +541,7 @@ As a result of the above terraform version detection additions, note these chang
   The runtime image is currently based on `debian:buster`, with the command run using `bash -xeo pipefail`.
 
   For example:
+
   ```yaml
   env:
     TERRAFORM_PRE_RUN: |
@@ -550,7 +567,7 @@ As a result of the above terraform version detection additions, note these chang
 
 ### Changed
 - Improved messaging in the workflow log when [terraform-apply](https://github.com/dflook/terraform-github-actions/tree/master/terraform-apply) is aborted because the plan has changed
-- Update documentation for `backend_config`, `backend_config_file`, `var_file` & `target` inputs to use separate lines for multiple values. 
+- Update documentation for `backend_config`, `backend_config_file`, `var_file` & `target` inputs to use separate lines for multiple values.
   Multiple values may still be separated by commas if preferred.
 
 ## [1.10.0] - 2021-05-30
@@ -587,9 +604,9 @@ As a result of the above terraform version detection additions, note these chang
 
 ### Deprecated
 - The `var` input has been deprecated due to the following limitations:
-  - Only primitive types can be set with `var` - number, bool and string.
-  - String values may not contain a comma.
-  - Values set with `var` will be overridden by values contained in `var_file`s
+  * Only primitive types can be set with `var` - number, bool and string.
+  * String values may not contain a comma.
+  * Values set with `var` will be overridden by values contained in `var_file`s
 
   `variables` is the preferred way to set input variables.