Skip to content

Fix zizmor warning in release workflow #2826

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamtheturtle merged 1 commit into from
Jan 3, 2026
Merged

Fix zizmor warning in release workflow #2826

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,8 @@ jobs:
uses: jacobtomlinson/gha-find-replace@v3
with:
find: "Next\n----"
replace: "Next\n----\n\n${{ steps.calver.outputs.release }}\n${{ steps.changelog_underline.outputs.underline\
\ }}"
replace: |-
Next\n----\n\n${{ steps.calver.outputs.release }}\n${{ steps.changelog_underline.outputs.underline }}\n
Copy link

@cursor cursor bot Jan 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Block scalar preserves literal \n instead of newlines

The change from a double-quoted string to a YAML literal block scalar (|-) breaks the newline handling. In double-quoted strings, \n is interpreted as a newline character, but in literal block scalars, \n is preserved as the literal two characters backslash and 'n'. The find field still uses a double-quoted string with actual newlines, but the replace field will now insert literal \n text instead of line breaks, corrupting the CHANGELOG.rst file format when the release workflow runs.

Fix in Cursor Fix in Web

include: CHANGELOG.rst
regex: false

Expand Down