A composite action must expose an output named bundle-path to the caller workflow. Where is the output declared, and how is its value produced at runtime?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Composite actions declare outputs in action.yml and map them to step outputs written with $GITHUB_OUTPUT. Branding and secrets inherit are not the output channel, and composites absolutely can export outputs.
Full explanation below image
Full Explanation
Composite actions support the same outputs pattern as other action types: define outputs in action.yml with a value expression such as ${{ steps.pack.outputs.path }}, ensure the referenced step has an id, and write path=... to GITHUB_OUTPUT inside that step. Callers then read steps.<step_id>.outputs.bundle-path after uses:. Repository variables are a separate configuration store, not action outputs. branding only controls Marketplace icon/color. secrets: inherit applies to reusable workflow secret forwarding, not composite action outputs. Remember each composite run: step also needs an explicit shell: field—that is orthogonal to outputs but commonly tested together when authoring composites.