Fix release notes backtick command substitution issue
Use --notes-file instead of --notes with variable expansion to prevent bash from interpreting markdown code blocks as shell commands. Fixes the error where installation examples like: ```bash docker pull rcourtman/pulse:v4.29.0 ``` Were being executed as actual commands during release creation. Related to #671
This commit is contained in:
parent
8a4e7e9de8
commit
5f05718c3e
1 changed files with 7 additions and 1 deletions
8
.github/workflows/release.yml
vendored
8
.github/workflows/release.yml
vendored
|
|
@ -220,11 +220,17 @@ jobs:
|
|||
# Use LLM-generated release notes
|
||||
NOTES="${{ steps.generate_notes.outputs.RELEASE_NOTES }}"
|
||||
|
||||
# Write notes to file to avoid bash interpreting backticks as commands
|
||||
NOTES_FILE=$(mktemp)
|
||||
echo "$NOTES" > "$NOTES_FILE"
|
||||
|
||||
# Create draft release with generated notes
|
||||
gh release create "${TAG}" \
|
||||
--draft \
|
||||
--title "Pulse ${TAG}" \
|
||||
--notes "$NOTES"
|
||||
--notes-file "$NOTES_FILE"
|
||||
|
||||
rm -f "$NOTES_FILE"
|
||||
|
||||
echo "release_url=$(gh release view ${TAG} --json url -q .url)" >> $GITHUB_OUTPUT
|
||||
echo "tag=${TAG}" >> $GITHUB_OUTPUT
|
||||
|
|
|
|||
Loading…
Reference in a new issue