Revert release workflow to working state before heredoc changes #19
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.
Problem
The release workflow has been failing since October 23rd with the following error:
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:
Back to escape sequence approach:
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
This restores the release workflow to a known working state as requested in issue #18.
Original prompt
💡 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.