这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Oct 24, 2025

Problem

The release workflow has been failing since October 23rd with the following error:

##[error]Invalid value. Matching delimiter not found 'ghadelimiter_c62aa20a-2e80-4e1f-9492-de0ef078d1a2'

This issue was introduced by recent attempts (PRs #15 and #17) to use heredoc syntax with a uuidgen-generated delimiter for handling multiline content in the "Read release.md and use it as a body of new release" step. While the heredoc approach aimed to properly handle multiline content, it wasn't being correctly recognized by GitHub Actions, causing all subsequent workflow runs to fail.

Solution

This PR reverts the problematic step (lines 76-84 in .github/workflows/release.yml) back to the escape sequence approach that was working successfully before. The workflow is now identical to commit 0fe48b9 from October 23rd, which had multiple successful runs.

Changed from heredoc approach:

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

Back to escape sequence approach:

r=$(cat ./chaiNNer/history.txt)
r="${r//'%'/'%25'}"                               # Multiline escape sequences for %
r="${r//$'\n'/'%0A'}"                             # Multiline escape sequences for '\n'
r="${r//$'\r'/'%0D'}"                             # Multiline escape sequences for '\r'
echo "RELEASE_BODY=$r" >> $GITHUB_OUTPUT

The escape sequence method is the recommended approach for handling multiline strings in GitHub Actions outputs and has been proven to work reliably in this workflow's history.

Verification

  • ✅ YAML syntax validated
  • ✅ No diff between current version and last working version (0fe48b9)
  • ✅ Code review passed
  • ✅ CodeQL security scan: 0 alerts

This restores the release workflow to a known working state as requested in issue #18.

Original prompt

This section details on the original issue you should resolve

<issue_title>Workflows broken</issue_title>
<issue_description>The release workflow is currently broken. I would like the action to be reset to before it started failing, before the workflow changed. This will be temporary until I am able to figure this out myself </issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: joeyballentine <34788790+joeyballentine@users.noreply.github.com>
@joeyballentine joeyballentine marked this pull request as ready for review October 24, 2025 18:30
Copilot AI changed the title [WIP] Fix broken release workflow by resetting actions Revert release workflow to working state before heredoc changes Oct 24, 2025
@joeyballentine joeyballentine merged commit 9dea290 into main Oct 24, 2025
Copilot AI requested a review from joeyballentine October 24, 2025 18:30
Copilot finished work on behalf of joeyballentine October 24, 2025 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workflows broken

2 participants