Problem

The release workflow was failing with the error:

Error: Unable to process file command 'output' successfully.
Error: Invalid value. Matching delimiter not found 'EOF'

This occurred in the step that reads the commit history and sets it as the release body.

Root Cause

The heredoc syntax used to capture multiline output had two issues:

1. Improper closing delimiter: Used echo EOF without quotes, which GitHub Actions' output parser didn't recognize as a proper closing delimiter
2. Potential content collision: Using "EOF" as a static delimiter could fail if the commit history content contains "EOF" on its own line

Solution

Updated the heredoc syntax in .github/workflows/release.yml (lines 76-84) to use proper GitHub Actions multiline output format with a unique delimiter:

Before:

{
  echo "RELEASE_BODY<<EOF"
  cat ./chaiNNer/history.txt
  echo EOF
} >> $GITHUB_OUTPUT

After:

delimiter="ghadelimiter_$(uuidgen)"
echo "RELEASE_BODY<<${delimiter}" >> $GITHUB_OUTPUT
cat ./chaiNNer/history.txt >> $GITHUB_OUTPUT
echo "${delimiter}" >> $GITHUB_OUTPUT

Changes

• Removed the braces wrapper and changed to sequential writes to $GITHUB_OUTPUT
• Added quotes around the closing delimiter
• Generated a unique delimiter using uuidgen to prevent collision with content

This ensures the closing delimiter is properly recognized by GitHub Actions and won't conflict with any content in the commit history, making the workflow more robust.

Testing

• ✅ YAML syntax validated with yamllint
• ✅ Tested heredoc format with edge cases (content containing "EOF")
• ✅ Code review passed with no issues
• ✅ Security scan passed (0 alerts)

• Fixes Workflow still failing #16

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.