[codex] chore: fix Windows release notes fence#207
Merged
Conversation
What was changed: - Modified .github/workflows/release-win.yml to use tilde code fences in generated release notes. Why this approach: - PowerShell treats backticks as escape characters, which collapsed the generated Markdown fence in the v1.10.0 release notes. - Tilde fences render as Markdown code blocks without PowerShell escaping. Tested: - actionlint .github/workflows/release-win.yml: passed - Updated v1.10.0 GitHub Release notes manually and verified the SHA256 block renders with a valid Markdown code fence
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes the generated Windows release notes Markdown fence for future version tags.
The v1.10.0 release workflow published correctly, but PowerShell treated the backtick fence as escaped text and collapsed the release body code fence. I manually fixed the published v1.10.0 notes and this PR changes the workflow template to use tilde fences instead.
Validation
actionlint .github/workflows/release-win.ymlpassed locally.v1.10.0GitHub Release body now has a valid SHA256 code block.macOS safety
Workflow text generation only. No macOS runtime or release behavior changes.