v2.2.1

🚀 Enhancements

fix: bypass GITHUB_OUTPUT for large payloads when filtering by workspace_enabled Dan Miller (@milldr) (#62)

## What - Stop forcing `atmos-include-settings: true` through the upstream `github-action-atmos-affected-stacks` action when `filter-by-workspace-enabled` is set - Add a separate enrichment step that runs `atmos describe affected --include-settings` writing directly to file, bypassing `GITHUB_OUTPUT` - Remove redundant `printf` lines that wrote the output variable back to `affected-stacks.json`

Why

• For large monorepos, including settings inflates the affected stacks JSON payload enough to exceed GitHub Actions' expression evaluator memory limit, causing OOM errors like: The maximum allowed memory size was exceeded while evaluating the following expression: steps.affected.outputs.affected
• The upstream action puts the entire JSON into $GITHUB_OUTPUT, and GitHub's expression evaluator chokes evaluating if conditions that reference it
• By writing the settings-enriched data directly to file (never to GITHUB_OUTPUT), the large payload stays out of the expression evaluator entirely

Ref

• Follow-up to the filter-by-workspace-enabled feature added in this branch