v5.7.1

fix: Trigger release @goruha (#128)

## what * Added whitespace to trigger release

Why

• The latest release failed to be cut due test failure. Test fixed, so we need to issue a new release

References

• https://github.com/cloudposse/github-action-atmos-terraform-plan/actions/runs/20932787693

feat: Add `has-changes` output to expose plan change detection @jamengual (#125)

## Summary

• Adds a new has-changes output that exposes whether the Terraform plan contains infrastructure changes
• The output is a string value of "true" or "false"

Motivation

Currently, consumers who want to conditionally run steps based on whether the plan has changes must parse the summary output. The action already computes this internally (used for Infracost integration), but doesn't expose it.

This change simply exposes the existing steps.atmos-plan.outputs.changes value as a proper action output.

Usage

- uses: cloudposse/github-action-atmos-terraform-plan@v4
  id: plan
  with:
    component: mycomponent
    stack: dev

- if: steps.plan.outputs.has-changes == 'true'
  run: echo "Infrastructure changes detected"

Test plan

• Verify output is "true" when plan has changes
• Verify output is "false" when plan has no changes

🚀 Enhancements

Fix tests @goruha (#127)

This pull request introduces a minor improvement to the GitHub Actions workflow and action metadata. The main changes involve cleaning up formatting in the workflow output and adding a new output to the action.

Action output enhancement:

• Added a new output has-changes to action.yml, which indicates whether the Terraform plan has changes, with the value being the string 'true' or 'false'.

Workflow formatting cleanup:

• Removed unnecessary blank lines in the expected and actual output sections of .github/workflows/test-failed-plan-drift.yml to improve output readability and consistency. [1] [2]