fix: skip output evaluation when capture-output is disabled#48
Merged
Conversation
The outputs block in composite actions always evaluates its expressions, even when the step output is empty. GHA's template engine hits a memory limit processing the step context from large deployments. Fix by referencing a forwarding step that is skipped entirely when capture-output is false, preventing the expression evaluation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Maximum object size exceedederror that occurs even withcapture-output: falseoutputsblock always evaluates${{ steps.command.outputs.stdout }}, and GHA's template engine OOMs on the step context from large deploymentsforward-outputstep that is skipped whencapture-outputis false, so the expression inoutputsreferences a step with no outputs → evaluates to emptyContext
PR #47 added
capture-output: falseto skip writing stdout to$GITHUB_OUTPUT, but theoutputs:block still referencedsteps.command.outputs.stdout. GHA evaluates this expression after all steps complete, and it hits the memory limit on the step context from large Pulumi deployments (Portal has 6 services with verbose logs).Test plan
capture-output: falsesucceeds without OOM error🤖 Generated with Claude Code