(fix): Fix nested action outputs - #27
Merged
Ompragash merged 3 commits intoAug 20, 2026
Merged
Conversation
Parse action.yml from the subdirectory in uses (owner/repo/path@ref) so path-based composite actions export outputs to Harness. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid Docker 29.7.0 CopyToContainer regression that breaks act when copying actions under /var/run/act. Co-authored-by: Cursor <cursoragent@cursor.com>
Ompragash
approved these changes
Aug 18, 2026
Ompragash
left a comment
Ompragash
left a comment
Member
There was a problem hiding this comment.
LGTM. confirmed the nested action exports
5 tasks
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
2 participants
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
action.yml, so path-based actions (owner/repo/path/to/action@ref) never exported outputs to Harness.ParseLookupnow returns the action subdirectory, and we resolve<clone>/<path>/action.yml(with path-traversal guards). Root-level actions are unchanged..github/actions/...) that run successfully but leave Harness output variables empty (No output variables detected in action.yml; skipping output file generation.).docker:dindtodocker:29.6.0-dindto avoid Docker 29.7.0CopyToContainerregression (path escapes from parentunder/var/run/act).ActionDirtraversal cases that only escape afterfilepath.Clean.Test plan
uses, nested outputs, missing nestedaction.ymlsoft-fail, and path-traversal rejectiondocker run --rm -v "$PWD":/src -w /src golang:1.22.7 go test ./... -count=1 -vfjunior87/ci-py-test/.github/actions/sample-tag@main)Path: .github/actions/sample-tagoutput variablesstep runsnew_tag,new_version)plugins/github-actions:latestfails the same nested repro (empty outputs)mathieudutour/github-tag-action@v6.2) with pinned DinD base — nopath escapes from parentfailure; outputs exported