Bug
In workflow_call-compiled lock files, agent artifacts can be uploaded with a prefixed name but later downloaded using an unprefixed name.
Example mismatch observed after recompilation:
- Upload:
${{ needs.activation.outputs.artifact_prefix }}agent
- Download (conclusion path):
agent
Impact
When the unprefixed download misses, the follow-up setup step does not set GH_AW_AGENT_OUTPUT, which can break downstream safe-output processing in that job path.
Expected
All safe_outputs download steps should use the same prefixed artifact naming contract as the corresponding upload step in workflow_call context.
Note
The same lock file can contain another download step that correctly uses the prefixed name, suggesting inconsistent generation across code paths.
Bug
In workflow_call-compiled lock files, agent artifacts can be uploaded with a prefixed name but later downloaded using an unprefixed name.
Example mismatch observed after recompilation:
${{ needs.activation.outputs.artifact_prefix }}agentagentImpact
When the unprefixed download misses, the follow-up setup step does not set
GH_AW_AGENT_OUTPUT, which can break downstream safe-output processing in that job path.Expected
All safe_outputs download steps should use the same prefixed artifact naming contract as the corresponding upload step in workflow_call context.
Note
The same lock file can contain another download step that correctly uses the prefixed name, suggesting inconsistent generation across code paths.